MongoDB Node.js Driver SRV parent-domain check bypass
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- Present
- Impact type
- —
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA.
Summary
MongoDB Node.js Driver versions from 3.3.3 before 7.8.0 validate DNS SRV host names against the connection string's parent domain, then build the connection address from the original name, where certain characters end the host name early. An unauthenticated attacker who can forge or alter the DNS SRV response can redirect a mongodb+srv:// connection to a host they choose. TLS does not stop this, because the driver verifies the certificate against the redirected host name, which can expose application data and credentials and alter query results. Applications using mongodb:// connection strings are not affected.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
Description from the CNA
A validation flaw in the DNS SRV host discovery of the MongoDB Node.js driver may cause the driver to connect to a host outside the expected domain. For a mongodb+srv:// connection string, the driver checks each host name in the DNS SRV response against the domain of the connection string. The driver then builds the connection address from the original name, in which certain characters end the host name early. An unauthenticated party who can forge or change the DNS SRV response may redirect the connection to a host of their choice. TLS does not prevent this, because the driver verifies the server certificate against the redirected host name. This may result in unintended disclosure of application data and authentication credentials, and in altered query results. Applications that use mongodb:// connection strings are not affected.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
Upgrade the MongoDB Node.js Driver to version 7.8.0 or later.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
- Fix · CNA Node.js Driver (MongoDB) Fixed in 7.8.0
Timeline
- 2026-11-12 Threatist record created from CVE-2026-126837
- 2026-11-12 Weakness changed · CNA
- 2026-11-13 CISA SSVC decision points changed
References
More MongoDB vulnerabilities
- TI-2019-08023 Remote code execution in mongo-express via toBSON endpoints KEVCVSS 3.1CRITICAL 9.9
- TI-2025-13542 Zlib header length mismatch in MongoDB Server allows memory read KEVCVSS 4.0HIGH 8.7
- TI-2026-89295 MongoDB Server Missing Authorization Check in Replication Administrative Command CVSS 4.0HIGH 8.6
- TI-2026-89289 Incorrect authorization in MongoDB Server allows admin access CVSS 4.0HIGH 8.6
- TI-2026-79432 BSON output corruption via out-of-range binary subtype in MongoDB C# Driver CVSS 4.0MEDIUM 6.9
- TI-2026-79424 NoSQL command injection via mismatched BSON length in MongoDB C# Driver CVSS 4.0MEDIUM 6.9
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences