Unauthenticated service interruption via GSSAPI double-free
Published Aug 27, 2026 · Updated Aug 27, 2026
Double-free in MongoDB Connector for BI 2.4.0 through 2.14.29 allows remote attackers to crash mongosqld via Kerberos authentication. The GSSAPI error path releases the same allocation twice while processing a crafted authentication exchange, terminating the process. The service must be network-reachable with Kerberos enabled; the result is a BI Connector service interruption until mongosqld restarts.
Summary
What happened
Double-free in MongoDB Connector for BI 2.4.0 through 2.14.29 allows remote attackers to crash mongosqld via Kerberos authentication. The GSSAPI error path releases the same allocation twice while processing a crafted authentication exchange, terminating the process. The service must be network-reachable with Kerberos enabled; the result is a BI Connector service interruption until mongosqld restarts.
The record
- CVE
- CVE-2026-75159
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- MongoDB
- Product
- MongoDB Connector for BI
- Classifications
- CWE-415, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 27, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 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.4.0 <2.14.30
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.
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