Heap overflow via oversized decrypted TLS record sequence in Windows Secure Channel stream
Published Sep 17, 2026 · Updated Sep 17, 2026
A heap-based buffer overflow exists in the TLS transport layer of the MongoDB C Driver when built with the Windows platform TLS backend. A remote endpoint that the client connects to, or an attacker able to impersonate or redirect the client's connection, can cause the driver to write attacker-supplied data outside the bounds of a heap allocation while processing incoming encrypted traffic. No authentication or user interaction is required, because the affected processing occurs before any application-level authentication completes. Successful exploitation may lead to memory corruption in the client process, disclosure of adjacent heap memory, or termination of the process.
Summary
What happened
A heap-based buffer overflow exists in the TLS transport layer of the MongoDB C Driver when built with the Windows platform TLS backend. A remote endpoint that the client connects to, or an attacker able to impersonate or redirect the client's connection, can cause the driver to write attacker-supplied data outside the bounds of a heap allocation while processing incoming encrypted traffic. No authentication or user interaction is required, because the affected processing occurs before any application-level authentication completes. Successful exploitation may lead to memory corruption in the client process, disclosure of adjacent heap memory, or termination of the process.
The record
- CVE
- CVE-2026-93393
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- MongoDB
- Product
- MongoDB C++ Driver
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=1.24.0 <=1.24.4
- Affected versionversion=1.25.0 <=1.25.4
- Affected versionversion=1.26.0 <=1.26.2
- Affected versionversion=1.27.0 <=1.27.6
- Affected versionversion=1.28.0 <=1.28.1
- Affected versionversion=1.29.0 <=1.29.2
- Affected versionversion=1.30.0 <=1.30.8
- Affected versionversion=2.0.0 <=2.0.2
- Affected versionversion=2.1.0 <=2.1.2
- Affected versionversion=2.2.0 <=2.2.4
- Affected versionversion=2.3.0 <=2.3.3
- Affected versionversion=2.4.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started