Skip to main content
Mallory
HighVulnerability

CVE-2026-95691: Use-after-free in OpenSSL QUIC client CRYPTO frame processing

Published Nov 10, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days10 mentions · peak 9 in a dayToday
CVSS8.1High · v3.1
EPSS0.19%9th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-95691CWE-416 · Use After Free

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

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.
Activity feed

Recent activity

10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
ghsa syntheticNews · Nov 10, 2026GHSA-q8c3-jq6j-fc5fA heap-use-after-free read in the OpenSSL QUIC client occurs when a retransmitted CRYPTO frame fully overlaps an existing frame and releases storage still referenced by TLS handshake processing. A malicious QUIC server could cause client denial of service or limited heap-information disclosure, including identification of one allocator-adjacent byte through the protected Handshake response. The OpenSSL FIPS module is not affected because QUIC is outside its boundary.Read more ↗openssl libraryNews · Nov 10, 2026Vulnerabilities 4.1 | OpenSSL LibraryLow-severity heap-use-after-free read in the OpenSSL QUIC client. A retransmitted CRYPTO frame that fully overlaps an existing frame can release packet storage while TLS handshake processing retains a pointer into it. A malicious server can trigger client denial of service or disclosure of one allocator-adjacent byte through the protected Handshake response. Affected versions are 4.1.0 before 4.1.1, 4.0.0 before 4.0.4, and 3.5.0 before 3.5.10. The FIPS module is unaffected because QUIC is implemented outside its boundary.Read more ↗tenable nessus pluginsNews · Nov 10, 2026Linux Distros Unpatched Vulnerability : CVE-2026-95691 | Tenable®A heap-use-after-free read in the OpenSSL QUIC client allows a malicious QUIC server to cause client denial of service or limited heap-information disclosure. Fully overlapping retransmitted CRYPTO frames can prematurely release storage still referenced by TLS handshake processing. The server can identify one allocator-adjacent byte through the client's protected Handshake response. The OpenSSL FIPS module is unaffected. Although an upstream fix exists in OpenSSL 3.5.10, this Nessus plugin identifies distribution packages for which no vendor-supplied patch or solution is available.Read more ↗tenable nessus pluginsNews · Nov 10, 2026OpenSSL 4.0.0 < 4.0.4 Multiple Vulnerabilities | Tenable®Retransmitted QUIC CRYPTO frames can release packet storage while TLS handshake processing retains a pointer to it. The resulting use-after-free read can crash an OpenSSL QUIC client or expose a small amount of heap information. The FIPS module is unaffected. The plugin identifies affected OpenSSL 4.0 releases before 4.0.4 and recommends upgrading to 4.0.4 or later; the description also identifies a fix in 3.5.10 for the affected 3.5 branch.Read more ↗
+4 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.