CVE-2026-124709

7.5High

Published 17 Nov 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.1-flash-lite

7.5CVSS

High

0CVSS v3.110

Attack vector
Network
Complexity
Low
Privileges
None
User action
None
Impact
High impact on availability
Weakness
CWE-401

What an attacker gets

Remote attackers can crash your QUIC server by exhausting its memory. They need to establish a long-lived connection and repeatedly open and reset streams.

Root cause

The server fails to release stream memory if the peer sends a RESET_STREAM before the server's STOP_SENDING frame is acknowledged.

Affected versions

OpenSSL versions prior to the 2026-11-17 security release.

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Fix & remediation

Upgrade to OpenSSL 3.4.1, 3.3.3, 3.2.4, or 3.1.8 depending on your current branch. If you cannot patch immediately, limit the maximum number of concurrent streams allowed per connection.

remediation — bash
$ sudo apt-get update && sudo apt-get install --only-upgrade openssl

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD 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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-124709