Skip to main content
CVE-2026-129929VulnerabilityPublished

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

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-129929· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 7.9.1 when convenient.

Data as of 19 Nov 2026, 22:07 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (mongodb)CVSS 4.06.3
CNA (mongodb)CVSS 3.13.7
Patch
Available – fixed in 7.9.1
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Node.js Driver and mongodb to 7.9.1.

Affected software

ProductAffectedFixed in
MongoDBNode.js DriverAffected
  • <7.9.1
Fixed in
  • 7.9.1
npmmongodbpkg:npm/mongodbOther threatsAffected
  • <7.9.1
Fixed in
  • 7.9.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

References

Community reviews

Loading reviews…