Skip to main content
Menu
CVEs

CVE

OpenSSL memory leak in QUIC server for rejected streams

CVE-2026-124709EUVD-2026-126928GHSA-V2XH-2VWR-XQ7G

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H · openssl rates this low

7.5HighCISA-ADP
Exploited
No known exploitation
Fix
Fixed in 4.1.1, 4.0.4, 3.5.10
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10.

Published
Last modified
Reference
Last checked
0.19% · 8th percentile
48/100 · provisional
Low (openssl)
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

OpenSSL's QUIC server keeps state for rejected streams when the peer resets them before the rejection is signalled. A remote client that completes the QUIC handshake can repeatedly open and reset streams, growing server memory until the process runs out of memory and its connections are lost.

Written by a model from the sources below. Verify against them.

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

cve.now Index

48Pcve.now Index 48 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach20/20Affects OpenSSL (software on nearly every server, desktop or phone)
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 93 if added to CISA KEV
  • Would score about 88 if CISA's SSVC rates exploitation active
  • Would score about 53 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-124709 (Unbounded Memory Retention in QUIC Server for Rejected Streams), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-124709 (entry last updated 2026-11-17):
Affected:
- OpenSSL OpenSSL: from 4.1.0, fixed in 4.1.1; from 4.0.0, fixed in 4.0.4; from 3.5.0, fixed in 3.5.10
Fixed versions: 4.1.1, 4.0.4, 3.5.10.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-124709 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124709 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://openssl-library.org/news/secadv/20261117.txt
- https://github.com/openssl/openssl/commit/ead311df1037e7994a6d86c7e862d71ad59c52c7
- https://github.com/openssl/openssl/commit/22291a6af12f158fbb13bfbd572a33dbdbf290d2
- https://github.com/openssl/openssl/commit/f3acb0a3328046741479482c51cec815839e1b05
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-124709
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-124709"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated
  5. Posted on X by cve.now

Affected versions

  • OpenSSL OpenSSL

    From 4.1.0 · fixed in 4.1.1; From 4.0.0 · fixed in 4.0.4; From 3.5.0 · fixed in 3.5.10

Evidence 6

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Advisory
  2. Patch
  3. Patch
  4. Patch

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-124709

Is CVE-2026-124709 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-124709?

OpenSSL: from 4.1.0 before 4.1.1; from 4.0.0 before 4.0.4; from 3.5.0 before 3.5.10.Source: cve.now feed data

How do I fix CVE-2026-124709?

Upgrade to a fixed version: 4.1.1, 4.0.4, 3.5.10.Source: cve.now feed data

Why is it rated 7.5 High?

CVSS 7.5 scores the worst case. openssl rates it Low.

More CVEs