CVE
MongoDB Rust Driver credential disclosure in CSFLE KMS debug output
- Exploited
- No known exploitation
- Fix
- Fixed in 3.9.1, 3.8.2, 3.5.2, 3.4.1, 3.2.5, and 5 more
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 3.9.1, 3.8.2, 3.5.2, 3.4.1, 3.2.5, or one of 5 more.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.07% · 0th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 6/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
A MongoDB Rust Driver component that holds client-side field level encryption settings includes key management service credential material in its diagnostic formatting output without redaction. An application that records or displays this formatted output may place that material where a party with read access to the application's diagnostic output can see it, which may result in unintended disclosure of key material.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.7/10CVSS 5.7
- No patch0/5No signal
What would change the score
- Would score about 61 if added to CISA KEV
- Would score about 56 if CISA's SSVC rates exploitation active
- Would score about 28 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 3.9.1, 3.8.2, 3.5.2, 3.4.1, 3.2.5, or one of 5 more.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126838 (Rust Driver public Client Debug output exposes CSFLE KMS master-key material), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126838 (entry last updated 2026-11-12):
Affected:
- MongoDB Rust Driver: from 3.9.0, fixed in 3.9.1; from 3.8.0, fixed in 3.8.2; from 3.5.0, fixed in 3.5.2; from 3.4.0, fixed in 3.4.1; from 3.2.0, fixed in 3.2.5; from 3.1.0, fixed in 3.1.1; from 3.0.0, fixed in 3.0.1; from 2.8.0, fixed in 2.8.2; from 2.7.0, fixed in 2.7.1; from 2.6.0, fixed in 2.6.1
Fixed versions: 3.9.1, 3.8.2, 3.5.2, 3.4.1, 3.2.5, 3.1.1, 3.0.1, 2.8.2, 2.7.1, 2.6.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126838 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126838 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://jira.mongodb.org/browse/RUST-2531
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126838
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126838"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- MongoDB Rust Driver
From 3.9.0 · fixed in 3.9.1; From 3.8.0 · fixed in 3.8.2; From 3.5.0 · fixed in 3.5.2; From 3.4.0 · fixed in 3.4.1; From 3.2.0 · fixed in 3.2.5; From 3.1.0 · fixed in 3.1.1; From 3.0.0 · fixed in 3.0.1; From 2.8.0 · fixed in 2.8.2; From 2.7.0 · fixed in 2.7.1; From 2.6.0 · fixed in 2.6.1
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126838
Is CVE-2026-126838 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-126838?
Rust Driver: from 3.9.0 before 3.9.1; from 3.8.0 before 3.8.2; from 3.5.0 before 3.5.2; from 3.4.0 before 3.4.1; from 3.2.0 before 3.2.5; from 3.1.0 before 3.1.1; from 3.0.0 before 3.0.1; from 2.8.0 before 2.8.2; from 2.7.0 before 2.7.1; from 2.6.0 before 2.6.1.Source: cve.now feed data
How do I fix CVE-2026-126838?
Upgrade to a fixed version: 3.9.1, 3.8.2, 3.5.2, 3.4.1, 3.2.5, or one of 5 more.Source: cve.now feed data