Quick answers
- Is CVE-2026-75806 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-75806 being exploited in the wild.
- How severe is CVE-2026-75806?
- Medium severity, with a CVSS score of 5.3, published 29 September 2026.
- Which products and versions are affected?
- OpenSSL 1.1.1 and 3.0.
- Is there a fix for CVE-2026-75806?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-75806 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-75806?
- Check whether you run OpenSSL 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
The vulnerability is in the record layer validation for DTLS 1.2 connections protected by AEAD cipher suites. When a record shorter than the mandatory explicit IV and authentication tag overhead is received, the cipher implementation rejects the length but the record layer incorrectly treats this as an internal failure instead of a failed authentication check. An unauthenticated attacker with network access to the DTLS association can inject a malformed datagram to trigger connection termination without knowing any session keys.
Affected products
- OpenSSL OpenSSL 1.1.1 and 3.0
Timeline
- 2026-09-29: disclosed