OpenSSL · OpenSSL · published 2026-11-10
CVE-2026-95691Retransmitted QUIC CRYPTO Frames Can Cause DoS or One-byte Disclosure
Routine No exploitation evidence; EPSS 0.3%.
CVE-2026-95691 is not known to be exploited in the wild. EPSS estimates a 0.3% chance of exploitation in the next 30 days, higher than 21% of all CVEs. This OpenSSL vulnerability: CVSS 8.1 (v3.1). Fixed upstream in OpenSSL 4.1.1, 4.0.4, 3.5.10, 3.0.24 (+2 more); Debian and Ubuntu still have unfixed releases. Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in OpenSSL 4.1.1, 4.0.4, 3.5.10, 3.0.24, 1.1.1zk, 1.0.2zt.
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 | No fix yet |
| 12 bookworm | openssl | Not affected | |
| Ubuntu (+4 more packages) | 26.04 LTS | openssl | No fix yet |
| 24.04 LTS | openssl | No fix yet | |
| 22.04 LTS | openssl | No fix yet |
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: 5 CVEs
Upgrade to
4.1.14.0.43.5.103.0.241.1.1zk1.0.2ztWhy: Vendor security release for server software (most severe: CVE-2026-95691).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.3% (21th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 8.1 (v3.1)CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- OpenSSL OpenSSL
4.1.0to before4.1.1(affected)4.0.0to before4.0.4(affected)3.5.0to before3.5.10(affected)
Description (from the CVE record)#
Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage while the TLS record layer retains a direct pointer into that storage causing use after free. Impact summary: A malicious QUIC server can cause a heap-use-after-free read in the OpenSSL QUIC client. The server can also identify one allocator-adjacent byte through the client's protected Handshake response. CWE: CWE-416: Use After Free Description: During CRYPTO stream processing, a pointer into the first frame's memory on the stream is lent to the TLS handshake processing. The memory must remain stable until it is processed and released. However the processing of retransmitted CRYPTO frames could release the memory if the retransmitted frame fully overlapped the existing frame. This then causes use-after-free read when the TLS handshake processing continues. The use-after-free read can lead to a Denial-of-Service of the client application or a minor leak of information about the heap memory contents that might be overwritten with other data, subsequently allocated by the application, to the peer. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.
Quoted from the CVE Program record.