Read the docs

Unbounded memory retention in OpenSSL QUIC server for rejected streams

Priority LOW 38CWE-401Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
Denial of service
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from CNA. Impact type from CWE-401.

Summary

OpenSSL versions from 4.1.0 before 4.1.1, from 4.0.0 before 4.0.4, and from 3.5.0 before 3.5.10 are affected. A QUIC server that rejects a stream opened by the peer keeps that stream's state (CWE-401) when the peer resets the stream before the rejection is signalled. A remote client that completes a QUIC handshake can repeatedly open and reset streams, so server memory grows without bound until the process runs out of memory, a denial of service. Growth is slow and requires a long-lived connection.

Written with Claude Haiku 5.5 from the sources below · 2026-11-17

Description from the CNA

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.

Why it matters now

Fix Fixed OpenSSL (OpenSSL): 4.1.1, 4.0.4, 3.5.10

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
OpenSSLOpenSSL4.1.0 to before 4.1.1; 4.0.0 to before 4.0.4; 3.5.0 to before 3.5.104.1.1, 4.0.4, 3.5.10Patch availableCNA
  • OpenSSL VendorOpenSSL Affected 4.1.0 to before 4.1.1; 4.0.0 to before 4.0.4; 3.5.0 to before 3.5.10 Fixed in 4.1.1, 4.0.4, 3.5.10 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:*——OpenSSL
  • cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* Versions — — ·OpenSSL

Remediation

Upgrade OpenSSL to 4.1.1, 4.0.4 or 3.5.10, which fix the issue. The sources list no fixed version for OpenSSL outside these branches.

Written with Claude Haiku 5.5 from the sources below · 2026-11-17

  • Fix · CNA OpenSSL (OpenSSL) Fixed in 4.1.1, 4.0.4, 3.5.10

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Advisory ·

    OpenSSL — openssl-library.org/news/secadv/20261117.txt

    3 records Highest priority Priority LOW 3 LOW

    Other records, highest priority first

    • TI-2026-92464 Use-after-free in OpenSSL PEM_X509_INFO_read_bio_ex() on failed readPriority LOW 38
    • TI-2026-92463 Out-of-bounds read in OpenSSL TLS key-share processing with Suite BPriority LOW 38

Timeline

  1. 2026-11-17 Threatist record created from CVE-2026-124709
  2. 2026-11-17 Alias added: GHSA-v2xh-2vwr-xq7g

References

  • TI-2022-01915 The c_rehash script allows command injection CVSS 3.1CRITICAL 9.8
  • TI-2021-02645 SM2 Decryption Buffer Overflow CVSS 3.1CRITICAL 9.8
  • TI-2009-03392 The TLS protocol, and the SSL protocol 3.0 and possibly earlier, as used in Microsoft… CVSS 3.1CRITICAL 9.8
  • TI-2022-01176 The c_rehash script allows command injection CVSS 3.1CRITICAL 9.8
  • TI-2014-00154 Out-of-bounds read in OpenSSL TLS and DTLS Heartbeat handling KEVCVSS 3.1HIGH 7.5
  • TI-2025-14107 Stack buffer overflow in CMS (Auth)EnvelopedData parsing CVSS 3.1HIGH 8.8
See all 328 →

Sources