MongoDB C# Driver traffic redirection in DNS SRV lookup
- Exploited
- No known exploitation
- Fix
- Fixed in 3.14.1
- Who is exposed
- Not reported
Summary
The MongoDB C# Driver can be tricked, remotely and without logging in, into connecting to a host outside its trusted domain. An attacker who can answer the client's DNS SRV lookup can insert a host they control into the server list by using a comma in the SRV target. Applications that resolve connection strings with the affected API and connect to the result may send their data, login credentials, and query results through that host, which can expose data and credentials and allow forged query results.
Written by a model
Original description
An improper neutralization of delimiters in the MongoDB C# driver's DNS SRV connection-string resolution lets an unauthenticated party who can answer the client's DNS SRV query place a host outside the trusted domain into the client's server list. When an application resolves the connection string through the affected API and connects with the result, application data, authentication credentials and query results may pass through that host. This may result in unintended disclosure of data and credentials and in forged query results.
What to do
Upgrade to a fixed version: 3.14.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-129938 (Attacker 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…), 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-129938 (entry last updated 2026-11-19):
Affected:
- MongoDB C# Driver: from 2.5.0, fixed in 3.14.1
Fixed versions: 3.14.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129938 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129938 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/CSHARP-6283
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-129938
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-129938"}.Affected versions
- MongoDB C# DriverFrom 2.5.0 · fixed in 3.14.1
cve.now Index
- Exploitation0/40No signal
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 9.1, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | jira.mongodb.org · browse/CSHARP-6283 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129938 |
| Record | NVD · CVE-2026-129938 |
Questions about CVE-2026-129938
Is CVE-2026-129938 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-129938?
C# Driver: from 2.5.0 before 3.14.1.
Source: cve.now feed data
How do I fix CVE-2026-129938?
Upgrade to a fixed version: 3.14.1.
Source: cve.now feed data
Related
- CVE-2026-114644Memory-exhaustion denial of service via unbounded symbol interning during BSON/JSON deserialization
- CVE-2026-126982Remote code execution via generic-type allow-list bypass in BSON object deserialization
- CVE-2026-114649Authentication bypass via issuer-and-serial-only certificate equality in shared cluster cache
- CVE-2026-114648NoSQL injection via dot and dollar characters in LINQ filter field names and dictionary keys
- CVE-2026-114653Silent client-side encryption bypass via unescaped field-name regex in CSFLE schema builder
- CVE-2026-114652Update operator injection via single-element list rewriting in the update builder
No corrections so far. Something wrong on this page? Report an error.