MongoDB PHP Driver credential exposure in connection string parse errors
- Exploited
- No known exploitation
- Fix
- Fixed in 1.21.14, 2.1.14, 2.5.8
- Who is exposed
- Not reported
Summary
The MongoDB PHP Driver can include the full connection string, credentials included, in the error it raises when that string fails to parse. An attacker with local access and low privileges who can influence any part of the connection string can cause those credentials to be written to standard error output and log files, where anyone able to read that output could see them.
Written by a model
Original description
The MongoDB PHP extension includes the full connection string it was given in the error it raises when that string cannot be parsed. A party able to influence any part of the connection string, including a part that holds no secret, can cause the resulting message to carry credentials into the application's standard error output and log files. This may result in unintended disclosure of authentication material to anyone able to read that output.
What to do
Upgrade to a fixed version: 1.21.14, 2.1.14, 2.5.8.
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-129928 (Credential exposure via unmasked connection string in driver parse-error messages for the PHP driver), 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-129928 (entry last updated 2026-11-19):
Affected:
- MongoDB PHP Driver: from 1.16.0, fixed in 1.21.14; from 1.22.0, fixed in 2.1.14; from 2.2.0, fixed in 2.5.8
Fixed versions: 1.21.14, 2.1.14, 2.5.8.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129928 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129928 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/PHPC-2804
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-129928
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-129928"}.Affected versions
- MongoDB PHP DriverFrom 1.16.0 · fixed in 1.21.14; From 1.22.0 · fixed in 2.1.14; From 2.2.0 · fixed in 2.5.8
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.8/10CVSS 6.8
- No patch0/5No signal
What would change the score
- Would score about 62 if added to CISA KEV
- Would score about 57 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | jira.mongodb.org · browse/PHPC-2804 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129928 |
| Record | NVD · CVE-2026-129928 |
Questions about CVE-2026-129928
Is CVE-2026-129928 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-129928?
PHP Driver: from 1.16.0 before 1.21.14; from 1.22.0 before 2.1.14; from 2.2.0 before 2.5.8.
Source: cve.now feed data
How do I fix CVE-2026-129928?
Upgrade to a fixed version: 1.21.14, 2.1.14, 2.5.8.
Source: cve.now feed data
Related
- CVE-2026-84968Heap out-of-bounds read via corrupt nested BSON in field path error message
- CVE-2025-12119Bulk write with options may read invalid memory
- CVE-2026-106436Application denial of service and data truncation via unchecked BSON append failures in MongoDB PHP Driver
- CVE-2026-96745PHP object injection via unsuppressible __pclass class inference in command monitoring events
- CVE-2026-106432Heap buffer overflow via 32-bit string-length truncation in MongoDB PHP Driver
- CVE-2026-129932Attacker able to redirect a Java driver client to a host they own, surviving TLS certificate verification, via an SRV parent-domain bypass
No corrections so far. Something wrong on this page? Report an error.