Heap buffer overflow via unsafe username copying
Published May 6, 2026 · Updated May 6, 2026
Heap buffer overflow in MongoDB C Driver 2.1.0 through 2.1.2 allows local users to corrupt memory through a crafted GSSAPI username. The Cyrus SASL username canonicalization path copies the URI username into a heap buffer without checking that the destination is large enough. The flaw triggers before authentication or network traffic, but requires an application to accept an untrusted username in a MongoDB URI with authMechanism=GSSAPI.
Summary
What happened
Heap buffer overflow in MongoDB C Driver 2.1.0 through 2.1.2 allows local users to corrupt memory through a crafted GSSAPI username. The Cyrus SASL username canonicalization path copies the URI username into a heap buffer without checking that the destination is large enough. The flaw triggers before authentication or network traffic, but requires an application to accept an untrusted username in a MongoDB URI with authMechanism=GSSAPI.
The record
- CVE
- CVE-2026-6691
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- MongoDB
- Product
- MongoDB C++ Driver
- Classifications
- CWE-120, CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 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.1.0 <=2.1.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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