MongoDB Go Driver credential leak in connection string parse errors
- Exploited
- No known exploitation
- Fix
- Fixed in 2.10.1
- Who is exposed
- Not reported
Summary
The MongoDB Go driver includes the raw value of a connection string query option in its parse error when that value has invalid percent encoding, so a secret such as a TLS key file password or AWS session token can appear in plain text. An attacker with local access and low-privileged read access to wherever the application records or displays that error can learn the secret, and no user action is needed.
Written by a model
Original description
The MongoDB Go driver's connection string parser includes the raw, undecoded value of a query option in the error it returns when that value contains invalid percent encodings. When the option holds a secret, such as a TLS key file password or an AWS session token, the secret appears in plain text in the error. A party with low-privileged read access to wherever the application records or displays that error may learn the secret.
What to do
Upgrade to a fixed version: 2.10.1.
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-129934 (Credential exposure via unmasked option values in Go driver connection string parse errors), 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-129934 (entry last updated 2026-11-19):
Affected:
- MongoDB GO Driver: from 1.0.0
- MongoDB GO Driver: from 2.0.0, fixed in 2.10.1
Fixed versions: 2.10.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129934 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129934 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/GODRIVER-4110
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-129934
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-129934"}.Affected versions
- go.mongodb.org/mongo-driverFrom 1.0.0
- go.mongodb.org/mongo-driver/v2From 2.0.0 · fixed in 2.10.1
cve.now Index
- Exploitation0/40No signal
- 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
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | jira.mongodb.org · browse/GODRIVER-4110 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129934 |
| Record | NVD · CVE-2026-129934 |
Questions about CVE-2026-129934
Is CVE-2026-129934 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-129934?
go.mongodb.org/mongo-driver: from 1.0.0. go.mongodb.org/mongo-driver/v2: from 2.0.0 before 2.10.1.
Source: cve.now feed data
How do I fix CVE-2026-129934?
Upgrade to a fixed version: 2.10.1.
Source: cve.now feed data
Related
- CVE-2026-107325Application denial of service via missing BSON array length validation in MongoDB Go Driver
- CVE-2026-107324Application denial of service via integer overflow in BSON value-length validation in MongoDB Go Driver
- CVE-2026-81521Cross-database write retargeting via unvalidated dotted database name in Client.BulkWrite in the MongoDB Go Driver
- CVE-2026-129935Authentication identity confusion via NUL-byte injection in SASL PLAIN credentials
- CVE-2026-88031GridFS data deletion via query-operator injection in file IDs in the MongoDB Go Driver
- CVE-2026-129932Attacker able to redirect a Java driver client to a host they own, surviving TLS certificate verification, via an SRV parent-domain bypass
No corrections so far. Something wrong on this page? Report an error.