Skip to main content
Menu
CVEs

MongoDB Python Driver credential exposure in driver object text output

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

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

Summary

A weakness in the MongoDB Python Driver causes a configuration option value that protects private key material to be written in clear text into the embedding application's output and log records when a driver object is converted to text. A local attacker with low privileges who can read those files can obtain the credential.

Written by a model

Original description

A credential-handling weakness in the MongoDB Python Driver allows a configuration option value that protects private key material to be written in clear text into the embedding application's own output and log records when a driver object is converted to text. A party able to read that output may obtain the credential. Obtaining it requires read access to the application's local output or log files.

What to do

Upgrade to a fixed version: 4.20.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-129927 (Credential exposure via unmasked option value in Python driver object text output), 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-129927 (entry last updated 2026-11-19):
Affected:
- MongoDB Python Driver: from 3.1, fixed in 4.20.1
Fixed versions: 4.20.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129927 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129927 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/PYTHON-6058
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-129927
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-129927"}.

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/PYTHON-6058
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-129927
RecordNVD · CVE-2026-129927

Questions about CVE-2026-129927

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

Python Driver: from 3.1 before 4.20.1.

Source: cve.now feed data

How do I fix CVE-2026-129927?

Upgrade to a fixed version: 4.20.1.

Source: cve.now feed data

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