Skip to main content
VulnerabilityPublished

CVE-2026-129924: MongoDB Ruby Driver · Generation of Error Message Containing Sensitive Information

Affects MongoDB Ruby DriverSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium : upgrade to 2.26.2 when convenient.

Data as of 19 Nov 2026, 19:49 UTC

CVSS 4.0 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (mongodb)CVSS 4.06.8
CNA (mongodb)CVSS 3.15.5
Patch
Available – fixed in 2.26.2
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade MongoDB Ruby Driver to 2.26.2.

Affected software

ProductAffectedFixed in
MongoDBRuby DriverAffected
  • >=2.0.3 <2.26.2
Fixed in
  • 2.26.2

AI-suggested

Upgrade the MongoDB Ruby driver to version 2.26.2 or later, where this vulnerability is fixed. No other mitigation is indicated or required by the vendor advisory.

Description

CVE-2026-129924 is a vulnerability in the MongoDB Ruby driver where error messages may expose sensitive information. When a connection string containing secrets cannot be parsed, the driver includes the unmasked connection string in the error output. This can lead to secret disclosure through application error logs or outputs accessible to an attacker. No special privileges or network access are required to trigger this error, only the ability to read the error output. The issue affects versions from 2.0.3 up to but not including 2.26.2 and is fixed in version 2.26.2.

References

Community reviews

Loading reviews…