MongoDB C# Driver credential disclosure in connection string parse errors
- Exploited
- No known exploitation
- Fix
- Fixed in 1.30.16, 2.5.9
- Who is exposed
- Not reported
Summary
The MongoDB C Driver includes unredacted connection-string option values in error messages when validation fails, so sensitive data an application placed in that field can be disclosed through the returned message and default standard error logging. An attacker with local access and low privileges who can influence the connection string given to the application can trigger this without any user action.
Written by a model
Original description
The MongoDB C Driver places a submitted connection-string option value into a diagnostic message without redaction when that option fails validation. The message is returned to the calling application and is also written to the process's standard error by the driver's default logging behavior. A party that can influence the connection string given to an application using the driver may cause that field's contents to be recorded, which may result in unintended disclosure of information the application placed in that field.
What to do
Upgrade to a fixed version: 1.30.16, 2.5.9.
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-129939 (Credential exposure via unmasked connection string in driver parse-error messages for the C driver), 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-129939 (entry last updated 2026-11-19):
Affected:
- MongoDB C Driver: from 1.9.0, fixed in 1.30.16; from 2.0.0, fixed in 2.5.9
Fixed versions: 1.30.16, 2.5.9.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129939 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129939 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/CDRIVER-6441
- https://github.com/mongodb/mongo-c-driver/security/advisories/GHSA-crh7-vpgx-6w5p
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-129939
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-129939"}.Affected versions
- MongoDB C DriverFrom 1.9.0 · fixed in 1.30.16; From 2.0.0 · fixed in 2.5.9
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.8/10CVSS 6.8
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 4
| Kind | Source |
|---|---|
| Vendor advisory 2Establishes: Affected and fixed versions. | |
| Advisory | GitHub · mongodb/mongo-c-driver · Advisory GHSA-crh7-vpgx-6w5p |
| Link | jira.mongodb.org · browse/CDRIVER-6441 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129939 |
| Record | NVD · CVE-2026-129939 |
Questions about CVE-2026-129939
Is CVE-2026-129939 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-129939?
C Driver: from 1.9.0 before 1.30.16; from 2.0.0 before 2.5.9.
Source: cve.now feed data
How do I fix CVE-2026-129939?
Upgrade to a fixed version: 1.30.16, 2.5.9.
Source: cve.now feed data
Related
- CVE-2026-120955MongoDB C Driver Modern GridFS mongoc_gridfs_bucket_download_to_stream() Aborts Application on Malformed GridFS Metadata
- CVE-2026-120678MongoDB C Driver leaks the decompressed reply buffer when an OP_COMPRESSED reply fails to parse (denial of service)
- CVE-2026-96746Heap buffer overflow via mid-scan command list growth in client topology monitoring
- CVE-2026-84964Heap corruption via OCSP request double free from crafted multi-URL certificate in TLS client
- CVE-2026-126823Atlas SQL JDBC driver loads a native library it did not write: NativeLoader tolerates a pre-existing libmongosqltranslate.so in a shared…
- CVE-2026-120956remote abort and memory disclosure from a malformed cursor.ns
No corrections so far. Something wrong on this page? Report an error.