Skip to main content
Menu
CVEs

MongoDB Node.js Driver identity confusion in SASL PLAIN authentication

CVE-2026-129929EUVD-2026-130677Published November 19, 2026, updated

6.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 7.9.1
Who is exposed
Not reported

Summary

The MongoDB Node.js Driver does not neutralize NUL characters in the user name and password values it uses for SASL PLAIN authentication. An attacker who can choose the login values an application passes to the driver can remotely, without logging in, make the receiving system read a different login name and secret than the application supplied. Authenticating as another account still requires that account's password, and only deployments that use SASL PLAIN are affected.

Written by a model

Original description

The MongoDB Node.js 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: 7.9.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-129929 (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-129929 (entry last updated 2026-11-19):
Affected:
- MongoDB Node.js Driver: fixed in 7.9.1
Fixed versions: 7.9.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129929 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129929 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/NODE-7828
- https://github.com/mongodb/node-mongodb-native/security/advisories/GHSA-prmg-mvj2-c4f7
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-129929
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-129929"}.

Affected versions

cve.now Index

23Pof 100 · provisional · methodology v3
  • 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

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 4

KindSource
Vendor advisory 2Establishes: Affected and fixed versions.
AdvisoryGitHub · mongodb/node-mongodb-native · Advisory GHSA-prmg-mvj2-c4f7
Linkjira.mongodb.org · browse/NODE-7828
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-129929
RecordNVD · CVE-2026-129929

Questions about CVE-2026-129929

Is CVE-2026-129929 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-129929?

Node.js Driver: before 7.9.1.

Source: cve.now feed data

How do I fix CVE-2026-129929?

Upgrade to a fixed version: 7.9.1.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.