CVE-2026-95691: Use-after-free in OpenSSL QUIC client CRYPTO frame processing
CVE-2026-95691 is a heap-use-after-free vulnerability in OpenSSL QUIC client CRYPTO stream processing. TLS handshake processing borrows a pointer into the first CRYPTO frame's packet storage, which must remain valid until processing completes. A fully overlapping retransmitted CRYPTO frame can prematurely release that storage while the TLS record layer retains the pointer. Subsequent handshake processing reads freed memory, potentially causing client denial of service or limited heap-information disclosure. Affected versions are OpenSSL 3.5.0 before 3.5.10, 4.0.0 before 4.0.4, and 4.1.0 before 4.1.1. The OpenSSL FIPS module is unaffected because QUIC is outside its boundary.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
A malicious QUIC server can cause a heap-use-after-free read in a connecting client, potentially crashing the application and denying service. Exploitation can also disclose limited heap contents, including data placed in the freed storage by subsequent application allocations. The server can identify one allocator-adjacent byte through the client's protected Handshake response. Arbitrary code execution and integrity compromise are not established.
Mitigation
If you can’t patch tonight, do this now.
No vendor-specified temporary workaround is identified.
Remediation
Patch, then assume compromise.
Apply the upstream fix available in the public OpenSSL repository or an equivalent vendor-supplied backport. Upgrade the relevant branch to OpenSSL 3.5.10, 4.0.4, or 4.1.1 when available; these releases are scheduled for December 1, 2026.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2026-95691 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-95691 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-95691?
- As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-95691.
- Is there a patch for CVE-2026-95691?
- Apply the upstream fix available in the public OpenSSL repository or an equivalent vendor-supplied backport. Upgrade the relevant branch to OpenSSL 3.5.10, 4.0.4, or 4.1.1 when available; these releases are scheduled for December 1, 2026.
- How severe is CVE-2026-95691?
- CVE-2026-95691 has a CVSS v3.1 score of 8.1 (High) and an EPSS score of 0.19% (9th percentile) as of Nov 17, 2026.
Recent activity
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.