CVE-2026-129933: MongoDB Java Driver · Improper Neutralization of Null Byte or NUL Character
Affects MongoDB Java DriverSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 5.15.0 when convenient.
Data as of 19 Nov 2026, 21:34 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 5.15.0
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 19 Nov 2026.
What to do
Upgrade Java Driver and org.mongodb/mongodb-driver to 5.15.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| MongoDBJava Driver | Affected
| Fixed in
|
Mavenorg.mongodb/mongodb-driverpkg:maven/org.mongodb/mongodb-driverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade the MongoDB Java Driver to version 5.15.0 or later, where this vulnerability is fixed. No other mitigation is indicated. If upgrading is not immediately possible, avoid using SASL PLAIN authentication or ensure that login values do not contain NUL characters.
Description
The MongoDB Java Driver does not neutralize NUL characters in the user name and password values it places into the message it builds for SASL PLAIN authentication. A party who can choose the login values that an application passes to the driver can alter where the fields of that message begin and end. This may result in a receiving system reading a login name and secret that differ from the values the application supplied. Authenticating as a different account still requires that account's password. Only deployments that use SASL PLAIN authentication are affected.