Skip to content
OpenAdvisories
High · 7.5 CVE-2026-124709 EUVD-2026-126928GHSA-v2xh-2vwr-xq7g

Unbounded Memory Retention in QUIC Server for Rejected Streams

Published Nov 17, 2026 · Updated Nov 17, 2026 · Assigned by openssl

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.

Affected products

VendorProductAffectedFixed
OpenSSL OpenSSL 4.1.0 – < 4.1.1, 4.0.0 – < 4.0.4, 3.5.0 – < 3.5.10 4.1.1

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Debian 14 openssl No fix yet —
Debian 13 openssl No fix yet —
ReleasePackageFixed inAdvisory
Ubuntu 26.10 edk2 +2 No fix yet —
Ubuntu 26.04 LTS edk2 +2 No fix yet —
Ubuntu 24.04 LTS edk2 +1 No fix yet —
Ubuntu 22.04 LTS edk2 +1 No fix yet —
Show 14 more (older releases, extended support, other products)
ReleasePackageFixed inAdvisory
Ubuntu Pro FIPS 20.04 LTS openssl No fix yet —
Ubuntu Pro FIPS 18.04 LTS openssl No fix yet —
Ubuntu Pro FIPS 16.04 LTS openssl No fix yet —
Ubuntu Pro FIPS-updates 24.04 LTS openssl-fips No fix yet —
Ubuntu Pro FIPS-updates 22.04 LTS openssl +1 No fix yet —
Ubuntu Pro FIPS-updates 20.04 LTS openssl No fix yet —
Ubuntu Pro FIPS-updates 18.04 LTS openssl No fix yet —
Ubuntu Pro FIPS-updates 16.04 LTS openssl No fix yet —
Ubuntu Pro FIPS-preview 22.04 LTS openssl +1 No fix yet —
Ubuntu Pro 22.04 LTS nodejs No fix yet —
Ubuntu Pro 20.04 LTS edk2 +1 No fix yet —
Ubuntu Pro 18.04 LTS edk2 +3 No fix yet —
Ubuntu Pro 16.04 LTS edk2 +2 No fix yet —
Ubuntu Pro 14.04 LTS openssl No fix yet —

Wolfi

ReleasePackageFixed inAdvisory
Wolfi rolling openssl-4.0-dev +2 No fix yet —

Advisories 1

References