Skip to main content
No exploitation reportedAwaiting NVD analysis

CVE-2026-95691

Retransmitted QUIC CRYPTO Frames Can Cause DoS or One-byte Disclosure

No exploitation reported by the sources we read.

  • Published2026-11-10
  • WeaknessCWE-416

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-11-1018:16CVE publishedCNA

Versions per branch

Products declared by the CNA1 product

As openssl, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • OpenSSLother versions: not affected
    Affected
    • ≥ 4.1.0, < 4.1.1fixed in 4.1.1semver
    • ≥ 4.0.0, < 4.0.4fixed in 4.0.4semver
    • ≥ 3.5.0, < 3.5.10fixed in 3.5.10semver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-10

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • edk2Ubuntu:Pro:20.04:LTSall versions · no fixed version listedand 1 other package
  • edk2Ubuntu:Pro:18.04:LTSall versions · no fixed version listedand 3 other packages
  • edk2Ubuntu:Pro:16.04:LTSall versions · no fixed version listedand 2 other packages
  • edk2Ubuntu:26.10all versions · no fixed version listedand 2 other packages
  • edk2Ubuntu:26.04:LTSall versions · no fixed version listedand 2 other packages
  • edk2Ubuntu:24.04:LTSall versions · no fixed version listedand 1 other package
  • edk2Ubuntu:22.04:LTSall versions · no fixed version listedand 1 other package
  • nodejsUbuntu:Pro:22.04:LTSall versions · no fixed version listed

18 more package ranges on OSV.dev

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Published
2026-11-10
Last Modified
2026-11-16
NVD status
Awaiting Analysis
GitHub Advisory
GHSA-q8c3-jq6j-fc5f

Frequently asked questions

What is CVE-2026-95691?

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.

Is CVE-2026-95691 actively exploited?

Active exploitation of CVE-2026-95691 has not been confirmed. Its EPSS score was 0.2% on 2026-11-15, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-95691?

CVE-2026-95691 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H.

Running OpenSSL? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record