CVE-2026-44433: fallo de gravedad media en h2o quicly
Quicly is vulnerable to memory exhaustion
Publicada el · Actualizada el
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
13Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 5.3epss 0.5%
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Productos afectados
h2o · quiclyCVEs relacionadas — h2o quicly
En el mismo producto, de las más peligrosas a las menos.
CVE-2024-45396HIGHQuicly assertion failuresEPSS 0.6%CVE-2026-44436HIGHQuicly is vulnerable to connection state corruptionEPSS 0.5%CVE-2026-44435HIGHQuicly: Remote Denial of Service via assertion failure when CRYPTO stream handshake data exceeds 32KBEPSS 0.5%CVE-2025-61684HIGHQuicly has assertion failuresEPSS 0.4%CVE-2026-44434MEDIUMQuicly is vulnerable to stateless reset injectionEPSS 0.2%