CVE-2026-55367

7.5High

Published 04 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite

7.5CVSS

High

0CVSS v3.110

Attack vector
Network
Complexity
Low
Privileges
None
User action
None
Impact
High impact on availability
Weakness
CWE-770

What an attacker gets

Unauthenticated attackers can crash the H2O server by exhausting memory. This requires the server to have proxy.connect-udp enabled and to accept CONNECT-UDP requests.

Root cause

The server lacks a per-capsule buffer limit when processing incomplete CONNECT-UDP requests with large declared lengths.

Affected versions

H2O versions prior to commit 4212ce114506a073505fd389db16ad2ba4e582a0.

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Fix & remediation

Update H2O to commit 4212ce114506a073505fd389db16ad2ba4e582a0 or later. If you cannot update immediately, disable the proxy.connect-udp configuration directive.

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

NVD description

h2o is an HTTP server with support for HTTP/1.x, HTTP/2 and HTTP/3. Prior to commit 4212ce114506a073505fd389db16ad2ba4e582a0, a client could send an incomplete CONNECT-UDP Capsule with an excessively large declared length, causing H2O to keep buffering received bytes without a per-Capsule limit while waiting for the remainder. Deployments that enabled proxy.connect-udp and accepted CONNECT-UDP requests could exhaust server memory and lose availability. This vulnerability is fixed with commit 4212ce114506a073505fd389db16ad2ba4e582a0.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-55367