Application crash via wrapped SASL username size check
Published Sep 10, 2026 · Updated Sep 10, 2026
Integer overflow in MongoDB C Driver 2.2.0 through 2.5.2 allows local users to crash an embedding application via a crafted SASL username. The client-side authentication size check wraps for an unusually large username and then copies the value beyond a small buffer. Exploitation requires control of connection settings, an external SASL-enabled build, and a connection configured to use that backend.
Summary
What happened
Integer overflow in MongoDB C Driver 2.2.0 through 2.5.2 allows local users to crash an embedding application via a crafted SASL username. The client-side authentication size check wraps for an unusually large username and then copies the value beyond a small buffer. Exploitation requires control of connection settings, an external SASL-enabled build, and a connection configured to use that backend.
The record
- CVE
- CVE-2026-88035
- Published
- Sep 10, 2026
- Updated
- Sep 10, 2026
- Vendor
- MongoDB
- Product
- MongoDB .NET/C# Driver
- Classifications
- CWE-190, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 10, 2026CVE publishedPublication date reported by the CVE source.
- Sep 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.2.0 <2.5.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo