Skip to main content
Menu
CVEs

MongoDB C# Driver credential exposure via unmasked connection string parsing

CVE-2026-129936Published November 19, 2026, updated

5.7MediumCNA
Exploited
No known exploitation
Fix
Fixed in 3.14.1
Who is exposed
Not reported

Summary

The MongoDB C# Driver can include a connection string in its error messages when that string cannot be parsed, and some secret material in it is not masked. An attacker with low-privilege local access to the system where the driver runs, such as the ability to read the application's error output or logs, can see database authentication credentials that should have stayed hidden.

Written by a model

Original description

A MongoDB C# Driver component that interprets connection configuration supplied by the hosting application can include the caller-supplied configuration value in the text of the error it raises when that value cannot be interpreted. The redaction applied to that text does not cover all forms in which secret material may appear, so authentication material embedded in the configuration value can be preserved in the resulting error text and in anything that records it. Exploitation requires only the low privilege needed to observe the application's own error output or logs on the system where the driver runs; no database credentials or server connectivity are required. The result is disclosure of sensitive information to parties whose access to error output is broader than their intended access to the configuration secret.

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-129936 (Credential exposure via unmasked connection string in driver parse-error messages), 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-129936 (entry last updated 2026-11-19):
Affected:
- MongoDB C# Driver: from 2.0.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-129936 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129936 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-6205
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-129936
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-129936"}.

Affected versions

cve.now Index

6Pof 100 · provisional · methodology v3
  • 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

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Linkjira.mongodb.org · browse/CSHARP-6205
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-129936
RecordNVD · CVE-2026-129936

Questions about CVE-2026-129936

Is CVE-2026-129936 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-129936?

C# Driver: from 2.0.0 before 3.14.1.

Source: cve.now feed data

How do I fix CVE-2026-129936?

Upgrade to a fixed version: 3.14.1.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.