MongoDB Go Driver auth identity confusion in SASL PLAIN credentials
- Exploited
- No known exploitation
- Fix
- Fixed in 2.10.1
- Who is exposed
- Not reported
Summary
The MongoDB GO Driver does not neutralize NUL characters in user names and passwords it places into SASL PLAIN authentication messages, so an attacker who can reach it remotely without logging in and choose the login values an application passes to it may cause the receiving system to read a different login name and secret. Only deployments that use SASL PLAIN authentication are affected, and the attacker still needs the password of the account they are trying to impersonate.
Written by a model
Original description
The MongoDB Go Driver does not neutralize NUL characters in the user name and password values it places into the message it builds for SASL PLAIN authentication. A party who can choose the login values that an application passes to the driver can alter where the fields of that message begin and end. This may result in a receiving system reading a login name and secret that differ from the values the application supplied. Authenticating as a different account still requires that account's password. Only deployments that use SASL PLAIN authentication are affected.
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-129935 (Authentication identity confusion via NUL-byte injection in SASL PLAIN credentials), 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-129935 (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-129935 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129935 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-4120
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-129935
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-129935"}.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
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.3/10CVSS 6.3
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 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-4120 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129935 |
| Record | NVD · CVE-2026-129935 |
Questions about CVE-2026-129935
Is CVE-2026-129935 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-129935?
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-129935?
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-88031GridFS data deletion via query-operator injection in file IDs in the MongoDB Go Driver
- CVE-2026-129934Credential exposure via unmasked option values in Go driver connection string parse errors
- 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.