cve.bz

CVE-2026-107494 Unbounded QUIC RETIRE_CONNECTION_ID Frame Sending Queue

7.5 highEPSS 0.4%

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

On this page
Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL 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.4% estimated probability of exploitation activity in the next 30 days; 34th percentile. Scored 2026-11-22. 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-19. 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-770 Allocation of Resources Without Limits or Throttling
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-107494 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107494?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107494?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-107494 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
Ubuntu22.04:LTS, 24.04:LTS, Pro:20.04:LTSedk2, opensslno fix listedUBUNTU-CVE-2026-107494
Ubuntu26.04:LTS, 26.10edk2, openssl, edk2-hweno fix listedUBUNTU-CVE-2026-107494
UbuntuPro:14.04:LTS, Pro:FIPS-updates:16.04:LTS, Pro:FIPS-updates:18.04:LTS and 4 moreopensslno fix listedUBUNTU-CVE-2026-107494
UbuntuPro:16.04:LTSedk2, nodejs, opensslno fix listedUBUNTU-CVE-2026-107494
UbuntuPro:18.04:LTSedk2, nodejs, openssl and 1 moreno fix listedUBUNTU-CVE-2026-107494
UbuntuPro:22.04:LTSnodejsno fix listedUBUNTU-CVE-2026-107494
UbuntuPro:FIPS-preview:22.04:LTS, Pro:FIPS-updates:22.04:LTSopenssl, openssl-fipsno fix listedUBUNTU-CVE-2026-107494
UbuntuPro:FIPS-updates:24.04:LTSopenssl-fipsno fix listedUBUNTU-CVE-2026-107494
Alpaquita25, streamopensslno fix listedBELL-CVE-2026-107494
BellSoft Hardened Containers25, streamopensslno fix listedBELL-CVE-2026-107494

From the distributions' data via OSV.dev: Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Ubuntu · Alpaquita · BellSoft Hardened Containers.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is classified as Important severity because an unauthenticated remote attacker can remotely trigger severe memory exhaustion and crash the host application without requiring valid credentials or user intervention. Exposure is restricted to environments and applications actively utilizing OpenSSL's QUIC protocol stack to handle incoming network traffic. Deployments relying on conventional TLS connections or other transport protocols are not impacted by this flaw.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

ProductPackageStateAdvisory
Red Hat Hardened Imagescargo-nextestNot affected
Red Hat Hardened ImageschunkahAffected
Red Hat Hardened ImagesopenshellNot affected
Red Hat Hardened ImagesopensslAffected
Red Hat Hardened Imagesopenssl3Affected
Red Hat Hardened Imagespython3.13-maturinNot affected
Red Hat Hardened Imagespython-cryptographyAffected
Red Hat Hardened Imagesruby3.3Affected
Red Hat Hardened Imagesruby3.4Affected
Red Hat Hardened Imagesruby4.0Affected
Red Hat Hardened ImagesrustNot affected
Red Hat Hardened Imagesrust-bootupdAffected
Red Hat Hardened ImagesunboundAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-107494.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-770 (20).

History

  1. Scored 9.1 critical
  2. Score 9.1 → 7.5 high

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

References

Check your stackJSON