# CVE-2026-126837: Server-side request forgery in Node.js Driver

> Attackers who forge DNS SRV responses can redirect MongoDB Node.js driver connections to their host, leaking credentials and altering queries.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** Yes
- **Fix available:** No
- **Published:** 12 Nov 2026
- **Updated:** 13 Nov 2026

## What is CVE-2026-126837?

CVE-2026-126837 is a critical server-side request forgery vulnerability in MongoDB Node.js Driver, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-180 (Incorrect Behavior Order: Validate Before Canonicalize)

## Which versions are affected by CVE-2026-126837?

An affected version is only exploitable if your software uses the vulnerable function or option. Many projects that include it are not exposed.


## How do I fix CVE-2026-126837?

No fix has been published for CVE-2026-126837 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-126837 being exploited?

There is no known exploitation of CVE-2026-126837 in the wild and no public exploit code.

Public exploit code:

- Containerized differential lab and PoC for CVE-2026-126837: MongoDB Node.js driver 3.3.3-7.7.x validates SRV targets with an uncanonicalized endsWith, so '#', '?' or '/' in an SRV target redirects mongodb+srv clients to an attacker host, exposing SCRAM credentials. Proven on 7.7.0 vs 7.8.0; 42-payload sweep clean on the fixed line. (github_poc): https://github.com/googlesky/CVE-2026-126837

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126837 and fix it if it is affected.

What it is: CVE-2026-126837 is a critical server-side request forgery vulnerability in MongoDB Node.js Driver, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126837 in the wild and no public exploit code.
Exposure: An affected version is only exploitable if your software uses the vulnerable function or option. Many projects that include it are not exposed.

Affected product: MongoDB Node.js Driver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-126837/ (Markdown: https://insights.sbomify.com/CVE-2026-126837/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-126837
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126837
- OSV: https://osv.dev/vulnerability/CVE-2026-126837

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-126837/
Summaries are generated and may contain mistakes; the official description above is the record.
