MongoDB Node.js Driver credential exposure in connection string parse errors
- Exploited
- No known exploitation
- Fix
- Fixed in 7.9.1
- Who is exposed
- Not reported
Summary
The MongoDB Node.js Driver can include sensitive details from an application's connection string in the text of an error raised while that string is being parsed. An attacker with local access and low-privilege login who can read the application's error output or log files could obtain database credentials that the configuration would otherwise keep hidden.
Written by a model
Original 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.
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-129930 (Credential exposure via unmasked connection string in driver parse-error messages for the Node driver), 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-129930 (entry last updated 2026-11-19):
Affected:
- MongoDB Node.js Driver: from 4.0.0, 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-129930 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129930 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-7799
- https://github.com/mongodb/node-mongodb-native/security/advisories/GHSA-779g-w5r4-wr2x
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-129930
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-129930"}.Affected versions
- MongoDB Node.js DriverFrom 4.0.0 · fixed in 7.9.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 4
| Kind | Source |
|---|---|
| Vendor advisory 2Establishes: Affected and fixed versions. | |
| Advisory | GitHub · mongodb/node-mongodb-native · Advisory GHSA-779g-w5r4-wr2x |
| Link | jira.mongodb.org · browse/NODE-7799 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129930 |
| Record | NVD · CVE-2026-129930 |
Questions about CVE-2026-129930
Is CVE-2026-129930 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-129930?
Node.js Driver: from 4.0.0 before 7.9.1.
Source: cve.now feed data
How do I fix CVE-2026-129930?
Upgrade to a fixed version: 7.9.1.
Source: cve.now feed data
Related
- CVE-2026-126837Attacker able to redirect a client's database traffic to a host they control via special characters in an SRV target, bypassing the SRV…
- CVE-2026-119179MongoDB Node.js driver: Connection pool desynchronization after operation timeout can expose other user's data
- CVE-2026-129929Authentication identity confusion via NUL-byte injection in SASL PLAIN credentials
- CVE-2026-126835[Node.js Driver] OIDC ENVIRONMENT confusion bypasses ALLOWED_HOSTS and leaks human-callback bearer tokens
- 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
- CVE-2026-129938Attacker able to redirect a client's database traffic to a host they control via a comma in an SRV target, bypassing the SRV parent-domain…
No corrections so far. Something wrong on this page? Report an error.