MongoDB Ruby Driver credential exposure in connection string parse errors
- Exploited
- No known exploitation
- Fix
- Fixed in 2.26.2
- Who is exposed
- Not reported
Summary
The MongoDB Ruby Driver can include unmasked connection string content in the error it raises when a connection string cannot be parsed, which can expose any secret in that string in cleartext through application error output or logs. An attacker with local access and low-privilege login who can read that output can obtain the secret, and no user action is needed.
Written by a model
Original description
The MongoDB Ruby driver can include unmasked connection string content in the error it raises when a connection string cannot be parsed. If that connection string carries a secret, the secret may be disclosed in cleartext through the application's error output or logs. No privileges on the driver and no network access are needed to produce the error; a party able to read the application's error output may obtain the secret.
What to do
Upgrade to a fixed version: 2.26.2.
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-129924 (Credential exposure via unmasked connection string in driver parse-error messages for the Ruby 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-129924 (entry last updated 2026-11-19):
Affected:
- MongoDB Ruby Driver: from 2.0.3, fixed in 2.26.2
Fixed versions: 2.26.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129924 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129924 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/RUBY-3950
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-129924
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-129924"}.Affected versions
- MongoDB Ruby DriverFrom 2.0.3 · fixed in 2.26.2
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/RUBY-3950 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-129924 |
| Record | NVD · CVE-2026-129924 |
Questions about CVE-2026-129924
Is CVE-2026-129924 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-129924?
Ruby Driver: from 2.0.3 before 2.26.2.
Source: cve.now feed data
How do I fix CVE-2026-129924?
Upgrade to a fixed version: 2.26.2.
Source: cve.now feed data
Related
- CVE-2026-126818Mongoid 9.1.1 incomplete CVE-2026-93764 fix stores descendant-only encrypted fields in plaintext
- CVE-2026-129925Authentication identity confusion via NUL-byte injection in SASL PLAIN credentials
- CVE-2026-88030GridFS data disclosure and deletion via query-operator injection in file IDs in the MongoDB Ruby Driver
- CVE-2026-126817Mongoid stores encrypted fields in plaintext when two models share a collection
- 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
- CVE-2026-129938Attacker 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…
No corrections so far. Something wrong on this page? Report an error.