UNKNOWNCVSS not yet scoredVulnerability

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.

Properties

Last source
NVD
Nvd fetched at
2026-11-10T23:33:48.924589+00:00
Cve id
CVE-2026-95691
First seen by Signal
2026-11-10T19:28:56+00:00
Retrieved at
2026-11-10T23:34:23+00:00
Published at
2026-11-10T19:21:39.377
Last modified
2026-11-10T22:10:04.727

Related Entities (1)

HAS_WEAKNESS (1)

→[Weakness]Use After Free

Explore deeper with Ninja Signal's threat intelligence graph

CVE-2026-95691 — Ninja Signal Threat Intelligence | Ninja Signal