CVE-2026-44433

Quicly is vulnerable to memory exhaustion

Published Jul 16, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. Prior to commit 8b178e6, an adversarial peer could send a STREAM frame carrying just one byte at the largest offset being permitted to obtain additional flow control credit, which under certain circumstances could lead to a Denial of Service. Assuming the application prepares a receive buffer for storing all data that arrive out-of-order, up to the largest offset being received, this behavior could lead to the application allocating large amount of memory with the peer sending only a handful of packets, resulting in memory exhaustion. In addition to the receive buffer allocation strategy, the severity of this vulnerability depends on how the application controls the stream concurrency. In case of the H2O HTTP server, under its default setting, this bug increases the maximum amount of memory allocated per connection by about 4 times. This issue has been fixed by commit 8b178e6.

Analysis

AI-generated

Technical impact

The vulnerability exists in Quicly, an IETF QUIC protocol implementation that an attacker can send a single‑byte STREAM frame positioned at the largest offset allowed by the server to acquire additional flow control credit. Because Quicly prepares a receive buffer that can span up to the highest offset received, this crafted frame forces the application to allocate a large block of memory, even though only a handful of packets are sent. The resulting uncontrolled memory consumption can exhaust system RAM and lead to a denial‑of‑service. Additionally, the impact is amplified by the server’s stream concurrency configuration, which can increase per‑connection memory usage by roughly four times under default settings. This flaw is a classic uncontrolled resource consumption allocation limit problem (CWE‑770) and arises from untrusted input leading to resource exhaustion (CWE‑400).

Affected Systems

Affected vendors are the h2o:quicly project and any deployments that incorporate that library, notably the H2O HTTP server. All versions of Quicly managed before the commit 8b178e692c51a3b1031612ef89f03a53aac63c15 contain the bug. The fixer commit introduces corrected buffer sizing logic that prevents the excessive allocation triggered by large offset frames.

Risk and Exploitability

The CVSS score is 5.3, indicating a medium overall severity, while the EPSS score of less than 1 % suggests that the vulnerability is not widely exploited at present. The flaw does not appear in CISA’s KEV catalog. An attacker must be able to initiate a QUIC connection to the vulnerable service and craft a particular can serve as the adversary, so exposure to the internet indirectly raises the risk. If triggered, the server may consume large amounts of RAM, potentially leading to service disruption. Given the low EPSS, regular monitoring and patching remain the most effective mitigation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the upstream patch commit 8b178e6 to Quicly or upgrade to a version that includes this fix.
  • Reduce stream concurrency or adjust flow control credit settings in H2O to limit the maximum memory that can be allocated per connection.
  • Monitor server memory usage and implement alerts for sudden spikes to detect potential exploitation.

Generated by OpenCVE AI on July 31, 2026 at 01:08 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared H2o
H2o quicly
Vendors & Products H2o
H2o quicly
Type Values Removed Values Added
Description Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. Prior to commit 8b178e6, an adversarial peer could send a STREAM frame carrying just one byte at the largest offset being permitted to obtain additional flow control credit, which under certain circumstances could lead to a Denial of Service. Assuming the application prepares a receive buffer for storing all data that arrive out-of-order, up to the largest offset being received, this behavior could lead to the application allocating large amount of memory with the peer sending only a handful of packets, resulting in memory exhaustion. In addition to the receive buffer allocation strategy, the severity of this vulnerability depends on how the application controls the stream concurrency. In case of the H2O HTTP server, under its default setting, this bug increases the maximum amount of memory allocated per connection by about 4 times. This issue has been fixed by commit 8b178e6.
Title Quicly is vulnerable to memory exhaustion
Weaknesses CWE-400
CWE-770
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 17, 2026, 6:06 PM
Reserved
May 6, 2026, 2:40 PM
Status
Analyzed
Published
Jul 16, 2026, 11:16 PM
Modified
Oct 24, 2026, 8:10 PM