Back to feed
24Track

OpenSSL: Unbounded Memory Retention in QUIC Server for Rejected Streams

OpenSSL · CVE-2026-124709 ETK-2026-4652 EUVD-2026-126928 GHSA-V2XH-2VWR-XQ7G
0 news outlets1 CERTs and agencies0 research labs

Assessment: Track

SSVC decision points: exploitation none, automatable yes, technical impact partial, deployment high.

What is it?

Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned. Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service. CWE: CWE-401: Missing Release of Memory after Effective Lifetime Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected. The default configuration reaches this path. Once a connection has a default stream, meaning the application has rea

Evidence

Official warnings1National CERTs, government cyber security agencies and the vendor’s own advisories

Exploitation

  • Exploit code published (not verified by us)
  • Exploited in the wild (confirmed by a source)
  • Listed as known exploited (CISA KEV)
CVSS
7.5
EPSS
0.6%
First seen
1 d ago
Status
confirmed

All OpenSSL vulnerabilities