OpenSSL use-after-free read in QUIC client CRYPTO handling
Affects the QUIC client in OpenSSL 4.1, 4.0 and 3.5. Fixed in 4.1.1, 4.0.4 and 3.5.10.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.1.1, 4.0.4, 3.5.10
- Who is exposed
- Not reported
Summary
Written by a model
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.
Who should check
Teams running OpenSSL 4.1, 4.0 or 3.5 QUIC client code that connects to QUIC servers, including anyone shipping OpenSSL-based QUIC clients.
“OpenSSL 4.1, 4.0 and 3.5 are vulnerable to this issue.”
What to do
Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-95691 (Retransmitted QUIC CRYPTO Frames Can Cause DoS or One-byte Disclosure), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-95691 (entry last updated 2026-11-16):
Affected:
- OpenSSL OpenSSL: from 4.1.0, fixed in 4.1.1; from 4.0.0, fixed in 4.0.4; from 3.5.0, fixed in 3.5.10
Fixed versions: 4.1.1, 4.0.4, 3.5.10.
Conditions (all must be true for the bug to be hit):
- Affects OpenSSL 4.1, 4.0 and 3.5 (QUIC client) (source: https://openssl-library.org/news/secadv/20261110.txt)
- OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected (source: https://openssl-library.org/news/secadv/20261110.txt)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: adjacent access, no login, no user action.
CISA KEV: CVE-2026-95691 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-95691 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://openssl-library.org/news/secadv/20261110.txt
- https://github.com/openssl/openssl/commit/dd90ceb99a3c2ddba336bb4a00be9ebabd84c2a1
- https://github.com/openssl/openssl/commit/ec9d4de9d03989b29db5a3d7efdb4c285deaf386
- https://github.com/openssl/openssl/commit/f6244675833e097c2429a40d1b206d95385bd42f
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-95691
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-95691"}.Affected versions
- OpenSSL OpenSSLFrom 4.1.0 · fixed in 4.1.1; From 4.0.0 · fixed in 4.0.4; From 3.5.0 · fixed in 3.5.10
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. Advisories don't say whether default setups are affected
- Reach20/20Affects OpenSSL (software on nearly every server, desktop or phone)
- Severity8.1/10CVSS 8.1
- No patch0/5No signal
What would change the score
- Would score about 83 if added to CISA KEV
- Would score about 78 if CISA's SSVC rates exploitation active
- Would score about 50 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now6 days
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
- Posted on X by cve.now
Public exploit activity
- EPSS: 0.29%
- Posted on X by cve.now Nov 16
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | openssl-library.org · news/secadv/20261110.txt |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-95691 |
| Record | NVD · CVE-2026-95691 |
| Other links 3 | |
| Patch | GitHub · openssl/openssl · Commit dd90ceb9 |
| Patch | GitHub · openssl/openssl · Commit ec9d4de9 |
| Patch | GitHub · openssl/openssl · Commit f6244675 |
Questions about CVE-2026-95691
Is CVE-2026-95691 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
A heap use-after-free read in the QUIC client can crash the client application, which is a denial of service. It can also leak one allocator-adjacent heap byte to the server through the client's protected Handshake response.
Source: openssl-library.org
Which versions are affected by CVE-2026-95691?
OpenSSL: from 4.1.0 before 4.1.1; from 4.0.0 before 4.0.4; from 3.5.0 before 3.5.10.
Source: cve.now feed data
Am I affected, and how do I check?
OpenSSL 4.1, 4.0 and 3.5 are affected in their QUIC client. OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected. To check a installed version, run 'openssl version'.
Source: openssl-library.org
How do I fix CVE-2026-95691?
Upgrade to the fixed release for your line: OpenSSL 4.1.1, 4.0.4 or 3.5.10. The vendor names these fixes as the way to address the issue.
Source: openssl-library.org
Why is it rated 8.1 High?
CVSS 8.1 scores the worst case. openssl rates it Low.
Related
- CVE-2026-84782DTLS Retransmits Handshake Messages From a Stale Buffer Offset
- CVE-2026-107493Use-After-Free in PEM_X509_INFO_read_bio_ex() when appending to a caller-supplied stack fails
- CVE-2026-84786Possible NULL Dereference in Non-SMTP DANE Clients
- CVE-2026-121482Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with…
- CVE-2026-107494Unbounded QUIC RETIRE_CONNECTION_ID Frame Sending Queue
- CVE-2026-124709Unbounded Memory Retention in QUIC Server for Rejected Streams
No corrections so far. Something wrong on this page? Report an error.