CVE-2026-44433CWE-400CWE-770denial-of-service

CVE-2026-44433

Medium · published July 17, 2026

CVSS v3.1
5.3
EPSS
0%
Percentile
41.0
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
5.3 · MEDIUM
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
CVSS v4.0
Not supplied
EPSS
0.00488 · 41.0th percentile
Weaknesses
CWE-400 · Uncontrolled Resource Consumption; CWE-770 · Allocation of Resources Without Limits or Throttling
Published
2026-07-17T03:16Z
Affected products (1)
ProductVersionsFixed in
h2o/quicly< 2026-05-292026-05-29
References (2)
EPSS history
Timeline
  • 16 JUL 22:23Z
    Quicly is vulnerable to memory exhaustion
    cvelistv5