Quick answers
- Is CVE-2026-93393 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93393 being exploited in the wild.
- How severe is CVE-2026-93393?
- High severity, with a CVSS score of 8.1, published 17 September 2026.
- Which products and versions are affected?
- MongoDB C Driver before 1.30.11 and 2.5.4.
- Is there a fix for CVE-2026-93393?
- A patch was published on 2026-09-18: Fixed in C Driver 1.30.11 and 2.5.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93393 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-93393?
- Check whether you run MongoDB C Driver at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A heap-based buffer overflow exists in the TLS transport layer of the MongoDB C Driver when built with the Windows Secure Channel backend. The vulnerability occurs during TLS record processing after the handshake completes, triggered by a failure to properly validate decrypted TLS record size. A remote endpoint can cause the driver to write uncontrolled data outside the bounds of a heap allocation while processing incoming encrypted traffic. No authentication or user interaction is required since the processing occurs before application-level authentication. The vulnerability has been patched in versions 1.30.11 and 2.5.4.
Affected products
- MongoDB C Driver before 1.30.11 and 2.5.4
Timeline
- 2026-09-17: disclosed
- 2026-09-18: patched: Fixed in C Driver 1.30.11 and 2.5.4