cve.bz

CVE-2026-124709 Unbounded Memory Retention in QUIC Server for Rejected Streams

7.5 highEPSS 0.2%

High (7.5) in openssl openssl. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 9th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-11-17. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-401 Missing Release of Memory after Effective Lifetime
Published
Modified
Assigned by
openssl (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-124709 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-124709?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-124709?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-124709 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
OpenSSLfrom 4.1.0 before 4.1.1
OpenSSLfrom 4.0.0 before 4.0.4
OpenSSLfrom 3.5.0 before 3.5.10

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14opensslno fix listedDEBIAN-CVE-2026-124709

From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.

History

  1. Scored 7.5 high

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON