CVE-2026-129925: MongoDB Ruby Driver · Improper Neutralization of Null Byte or NUL Character
Affects MongoDB Ruby DriverSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.26.2 when convenient.
Data as of 19 Nov 2026, 19:49 UTC
Thin evidence
One scorer or none| CNA (mongodb) | CVSS 4.0 | 6.3 |
|---|---|---|
| CNA (mongodb) | CVSS 3.1 | 3.7 |
- Patch
- Available – fixed in 2.26.2
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| MongoDBRuby Driver | Affected
| Fixed in
|
AI-suggested
Upgrade the MongoDB Ruby Driver to version 2.26.2 or later, where this vulnerability is fixed. No other mitigation is indicated. If upgrading is not immediately possible, consider avoiding SASL PLAIN authentication or restricting the ability of untrusted parties to supply login credentials to the driver.
Description
CVE-2026-129925 is a vulnerability in the MongoDB Ruby Driver affecting versions from 2.0.0 up to but not including 2.26.2. It involves improper neutralization of NUL characters in the username and password fields used in SASL PLAIN authentication messages. This flaw allows an attacker who can control login values to manipulate message parsing, potentially causing the receiving system to interpret different credentials than those supplied by the application. Exploitation requires the attacker to know the password of the targeted account. Only deployments using SASL PLAIN authentication are affected. The issue is fixed in version 2.26.2.