OpenSSL · OpenSSL · published 2026-09-29
CVE-2026-75806Unauthenticated and Undersized DTLS 1.2 AEAD Record Causes DoS
Routine No exploitation evidence; EPSS 1.2%.
CVE-2026-75806 is not known to be exploited in the wild. EPSS estimates a 1.2% chance of exploitation in the next 30 days, higher than 69% of all CVEs. This OpenSSL vulnerability: CVSS 5.3 (v3.1), attacks can be automated. Fixed upstream in OpenSSL 4.0.3, 3.6.5, 3.5.9, 3.4.8 (+3 more); patched packages are out for Debian, Ubuntu and Red Hat Enterprise Linux; Red Hat Enterprise Linux still has unfixed releases. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in OpenSSL 4.0.3, 3.6.5, 3.5.9, 3.4.8, 3.0.23, 1.1.1zj, 1.0.2zs.
Linux distribution packages
If you run the distro’s package rather than an upstream build, this is the version to look for.
| Distro | Release | Package | Status |
|---|---|---|---|
| Debian | 13 trixie | openssl | Fixed in 3.5.7-1~deb13u3 |
| 12 bookworm | openssl | Fixed in 3.0.22-1~deb12u2 | |
| Ubuntu (+4 more packages) | 26.04 LTS | openssl | Fixed in 3.5.5-1ubuntu3.6 |
| 24.04 LTS | openssl | Fixed in 3.0.13-0ubuntu3.16 | |
| 22.04 LTS | openssl | Fixed in 3.0.2-0ubuntu1.30 | |
| Red Hat Enterprise Linux (+17 more packages) | RHEL 10 | openssl | Fixed in 3.5.9-1.el10_3 RHSA-2026:98588 |
| RHEL 9 | openssl | Fixed in 3.5.9-1.el9_9 RHSA-2026:98484 | |
| RHEL 8 | openssl | No fix yet | |
| RHEL 7 | openssl | No fix yet | |
| RHEL 6 | openssl | Won’t fix |
From the Debian Security Tracker, Ubuntu security notices (CC BY-SA 4.0) and Red Hat Security Data (CC BY 4.0). Check the distro link before acting.
Patch events
Crypto libraryOpenSSL
OpenSSL security fixes: 14 CVEs
Upgrade to
4.0.33.6.53.5.93.4.83.0.231.1.1zj1.0.2zsWhy: Vendor security release for server software (most severe: CVE-2026-84782).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 1.2% (69th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.3 (v3.1)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | Yes | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- OpenSSL OpenSSL
4.0.0to before4.0.3(affected)3.6.0to before3.6.5(affected)3.5.0to before3.5.9(affected)3.4.0to before3.4.8(affected)3.0.0to before3.0.23(affected)1.1.1to before1.1.1zj(affected)
Description (from the CVE record)#
Issue summary: An established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead. Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact. CWE: CWE-1284: Improper Validation of Specified Quantity in Input Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication. In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS. The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record. FIPS impact: no The affected code is outside the FIPS module boundary.
Quoted from the CVE Program record.