Skip to main content
VulnerabilityPublished

CVE-2026-129930: MongoDB Node.js Driver · Generation of Error Message Containing Sensitive Information

Affects MongoDB Node.js DriverSource CVE Database V5

0
Compare

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

Data as of 19 Nov 2026, 19:49 UTC

CVSS 4.0 base score
5.7Medium
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.05.7
CNA (mongodb)CVSS 3.14.7
Patch
Available – fixed in 7.9.1
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/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 18 Nov 2026.

What to do

Upgrade Node.js Driver and mongodb to 7.9.1.

Affected software

ProductAffectedFixed in
MongoDBNode.js DriverAffected
  • >=4.0.0 <7.9.1
Fixed in
  • 7.9.1
npmmongodbpkg:npm/mongodbOther threatsAffected
  • >=4.0.0 <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.

AI-suggested

Upgrade the MongoDB Node.js driver to version 7.9.1 or later where this vulnerability is fixed. No other mitigation is required as the fix is official and addresses the issue directly.

Description

A weakness in the MongoDB Node.js driver can place sensitive information taken from an application-supplied connection string into the text of an error produced while that connection string is being parsed. The error is generated inside the application process before any database connection is made, so no database account and no network access are needed for it to occur. A party able to read the application's error output or log files may thereby obtain database credentials that the application's configuration source would otherwise keep to a narrower audience.

References

Community reviews

Loading reviews…