Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

MongoDB Node.js Driver SRV Validation Flaw (CVE-2026-126837)

CVE-2026-126837 is a DNS SRV host validation flaw in the MongoDB Node.js Driver.

Reviewed by
Brandefense Analyst Team
Published
Reading Time
3 min read
CVE ID
CVE-2026-126837
Vendor
MongoDB
Affected Product
MongoDB Node.js Driver
Exploitation
Not confirmed
Published
2026-11-12

MongoDB says it may redirect an application using a mongodb+srv:// connection string to a host outside the expected domain.The MongoDB CNA rates the flaw 9.1 Critical under CVSS 4.0 and 7.4 High under CVSS 3.1. A party must be able to forge or alter the DNS SRV response for the affected connection.

What it allows

How Does CVE-2026-126837 Redirect Database Traffic?

For mongodb+srv:// connections, the driver checks DNS SRV host names against the connection string's parent domain. MongoDB says the driver then constructs the connection address from the original name rather than the validated form.

Certain characters can terminate that original host name early. A forged or altered SRV response can therefore pass the domain check while directing the connection elsewhere. The DNS hijacking glossary explains the broader redirection concept.

MongoDB says TLS does not stop this path because the driver checks the certificate against the redirected host name. The possible consequences are disclosure of application data and authentication credentials, plus altered query results.

The prerequisite is control over the DNS SRV response, not simply knowledge of a database address. For related product context, see our vulnerability intelligence platform page.

What Does the Available Evidence Say About Risk?

Brandefense Blackhole counted two dark chat posts mentioning CVE-2026-126837 from August 14 through November 12, 2026. These are post counts for that search term, not confirmed exploitation events.

CISA's KEV catalog version 2026.11.10 did not list this CVE. That catalog snapshot predates MongoDB's November 12 publication, so it cannot settle later exploitation status.

CVE-2026-126837 at a glance
Affected connection.
mongodb+srv:// with a forged or altered DNS SRV response.
Fixed driver.
7.8.0.
Direct mongodb:// connections.
Not affected.

Who is affected

Which MongoDB Node.js Driver Versions Are Affected?

The MongoDB CNA lists Node.js Driver versions 3.3.3 and later, up to but excluding 7.8.0, as affected. The affected path requires a mongodb+srv:// connection and an attacker-controlled or modified DNS SRV answer.

Applications using mongodb:// connection strings are not affected by this issue, according to the CNA. Check the installed driver package and the connection scheme used by each application. The MongoDB Server CVE-2026-118383 profile covers a separate server issue.

How Should Defenders Respond?

Update applications in the affected range to Node.js Driver 7.8.0 or a later supported release. Prioritize applications that use mongodb+srv:// and depend on DNS SRV answers outside a tightly controlled resolver path.

After deployment, verify the running application's installed driver version and connection scheme. As a Brandefense precaution, review database connection destinations and unexpected changes in query results. Investigate anomalies without treating either signal alone as proof of exploitation.

Timeline

  1. 2026-11-12

    MongoDB CNA published CVE-2026-126837 with an affected range from 3.3.3 to before 7.8.0 and a fixed boundary at 7.8.0.

What to do

  1. Inventory driver versions and connection schemes

    Identify applications using the MongoDB Node.js Driver from 3.3.3 to before 7.8.0. Record which use mongodb+srv://, because the CNA excludes mongodb:// connections.

  2. Upgrade the affected driver

    Update affected applications to Node.js Driver 7.8.0 or a later supported version. Prioritize mongodb+srv:// applications where DNS SRV responses can be forged or altered.

  3. Verify the running version after maintenance

    For npm deployments, run npm ls mongodb --all in the deployed application's directory and confirm each installed driver is 7.8.0 or later. Restart the application from that deployment, then verify its intended connection scheme and normal database connectivity.

  4. Review connection destinations

    As a Brandefense precaution, investigate unexpected database connection destinations, credential use, or altered query results. These observations require context and do not independently establish exploitation.

What Brandefense can do

Frequently Asked Questions

What is CVE-2026-126837?

It is a DNS SRV host validation flaw in the MongoDB Node.js Driver. A forged or altered SRV answer may redirect mongodb+srv:// traffic outside the expected domain.

Does TLS prevent CVE-2026-126837?

MongoDB says no. The driver validates the certificate against the redirected host name, so a TLS connection alone does not preserve the intended destination.

Which driver release fixes CVE-2026-126837?

The MongoDB CNA lists 7.8.0 as the fixed boundary. Verify that the running application has 7.8.0 or a later supported release after updating.

Are mongodb:// applications affected?

No. The MongoDB CNA says applications using mongodb:// connection strings are not affected by this SRV discovery flaw.

Sources

  1. CVE-2026-126837 recordMongoDB CNA via CVE Program
  2. CVE-2026-126837National Vulnerability Database
  3. Known Exploited Vulnerabilities CatalogCISA
ShareLinkedInX
Brandefense logo

Stay Ahead of Digital Threats.

Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.

Open The Full Demo Form →