CVE-2026-124709

Unbounded Memory Retention in QUIC Server for Rejected Streams

Published Nov 17, 2026 CVSS n/a EPSS n/a KEV · Not listed
Description
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 read from or written to the connection as
the tutorial server does, the effective incoming stream policy rejects streams
the application does not accept. Applications that set the REJECT policy
explicitly are affected too.

Each retained stream costs about 300 bytes, and the peer's stream credit
window paces how quickly they accumulate. A client that keeps the connection
open and keeps opening and resetting streams grows server memory without
bound. The severity is Low because growth is slow, needs a long-lived
connection, and causes no memory corruption or disclosure.

FIPS impact: no
The affected code is outside the FIPS module boundary.

Analysis

AI-generated

Technical impact

OpenSSL’s QUIC server can retain the state of streams that are rejected by the server if the peer resets those streams before the server has sent a STOP_SENDING frame. Each uncollected rejected stream consumes roughly 300 bytes of memory, and the peer’s stream credit window controls the rate at which these streams accrue. Over a long‑lived connections, an attacker can repeatedly open and reset streams, causing the server’s memory to grow without bound until the process exhausts available memory and all of its connections are lost. The vulnerability is a classic instance of CWE‑401, missing release of memory after effective lifetime, and leads to a DoS condition rather than corruption or disclosure. Doors to exploitation require a persistent QUIC connection, the client must honor the handshake and trigger stream resets, and the server must be running a configuration that rejects streams by default.

Affected Systems

OpenSSL QUIC servers that use the default stream rejection policy or that explicitly configure a REJECT policy. This includes any application built on OpenSSL that implements the QUIC protocol and does not apply the vendor‑provided patch. The advisory does not specify exact version ranges, but any OpenSSL release obtained before the patches referenced in the advisory is vulnerable.

Risk and Exploitability

The vulnerability’s low severity and the slow memory growth path reduce its immediate exploit impact, yet the possibility of exhausting system memory remains. Because memory leaks are not tied to buffer overflows or privilege escalation, the potential for cross‑process or normal user compromise is low, but the target system may experience a denial of service after sustaining a long‑lived QUIC session with many stream resets. The opportunistic nature of the attack and the lack of publicly available exploit code mean that this condition is not highly critical, yet it is significant enough to warrant a patch and monitoring. No known exploitation is present in the KEV catalog.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update OpenSSL to a version that includes the fix for the QUIC stream memory leak.
  • Reconfigure the QUIC stream policy to accept streams or throttle incoming streams to mitigate memory accumulation.
  • Implement connection timeout or rate limiting for QUIC streams to prevent prolonged memory buildup from repeated resets.

Generated by OpenCVE AI on November 17, 2026 at 09:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Openssl
Openssl openssl
Vendors & Products Openssl
Openssl openssl
Type Values Removed Values Added
Description 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 read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too. Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure. FIPS impact: no The affected code is outside the FIPS module boundary.
Title Unbounded Memory Retention in QUIC Server for Rejected Streams
Weaknesses CWE-401
References
Weaknesses
  • CWE-401

    Missing Release of Memory after Effective Lifetime

Sources

Status
PUBLISHED
Assigner
openssl
Published
Updated
Nov 17, 2026, 8:14 AM
Reserved
Nov 9, 2026, 10:45 AM
Status
Received
Published
Nov 17, 2026, 9:17 AM
Modified
Nov 17, 2026, 9:17 AM