Answer in brief
CVE-2026-93393 records a Critical severity (CVSS 9.2) vulnerability in Heap overflow via oversized decrypted TLS record sequence in Windows Secure Channel stream. The current sources do not mark it as known exploited. The current feed maps MongoDB Inc./C Driver (generic), MongoDB Inc./C Driver (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.2. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps MongoDB Inc./C Driver (generic), MongoDB Inc./C Driver (generic). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:mongodb:c_driver:*:*:*:*:*:mongodb:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| MongoDB Inc./C Drivergeneric | 2.4.0 || >=2.3.0 <=2.3.3 || >=2.2.0 <=2.2.4 || >=2.1.0 <=2.1.2 || >=2.0.0 <=2.0.2 || >=1.30.0 <=1.30.8 || >=1.29.0 <=1.29.2 || >=1.28.0 <=1.28.1 || >=1.27.0 <=1.27.6 || >=1.26.0 <=1.26.2 || >=1.25.0 <=1.25.4 || >=1.24.0 <=1.24.4 | Not reported |
| MongoDB Inc./C Drivergeneric | 2.4.0 || 2.3.0 || 2.2.0 || 2.1.0 || 2.0.0 || 1.30.0 || 1.29.0 || 1.28.0 || 1.27.0 || 1.26.0 || 1.25.0 || 1.24.0 | Not reported |
Published upstream
Sep 17, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 29, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
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 can cause the driver to write uncontrolled data outside the bounds of a heap allocation while processing incoming encrypted traffic after the TLS handshake completes. No authentication or user interaction is required, because the affected processing occurs before any application-level authentication completes. Triggering this issue may lead to memory corruption in the client process, disclosure of adjacent heap memory, or termination of the process.
Quoted source text, attributed separately from HOL analysis.