Bug 2577384 (CVE-2026-129933)

Summary: CVE-2026-129933 org.mongodb/mongodb-driver-core: MongoDB Java Driver: Authentication message manipulation via unneutralized null characters
Product: [Other] Security Response Reporter: OSIDB Bzimport <bzimport>
Component: vulnerabilityAssignee: Product Security DevOps Team <prodsec-dev>
Status: NEW --- QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: ant, ccranfor, cescoffi, fmongiar, gsmet, janstey, jmartisk, jnethert, jpechane, manderse, olubyans, ozzy, pjindal, rguimara, sbiarozk, tmielke, varjain
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: ---
Doc Text:
A flaw was found in the MongoDB Java Driver. The driver does not properly neutralize null characters in username and password values when constructing Simple Authentication and Security Layer (SASL) PLAIN authentication messages. An attacker capable of supplying login credentials to an application can exploit this vulnerability to manipulate message boundaries, causing the receiving server to interpret different credential fields than those originally provided. Successful authentication as another account still requires providing that target account's valid password.
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description OSIDB Bzimport 2026-11-19 20:42:44 UTC
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.