CVE-2026-44436: Quicly is vulnerable to connection state corruption
Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. Prior to commit 8b178e6, Quicly is vulnerable to a Denial of Service attack through connection state corruption. In QUIC Invariants, the maximum length of a Connection ID is 255 bytes, while QUIC version 1 further restricts the maximum to 20 bytes. Quicly implements QUIC version 1 and therefore its CID buffers are limited to 20 bytes. However, to be able to respond to unknown versions of QUIC, its packet decoder accepts Connection IDs of up to 255 bytes. As its CID buffers are merely 20 bytes long, Quicly must reject QUIC version 1 packets with Connection IDs longer than that. The command line tool bundled with Quicly has had that check, however the library itself lacked such enforcement. As a consequence, when used by applications that lack their own enforcement, the connection state becoming inconsistent to buffer overrun. Fortunately, the overflow stops within the allocated chunk of memory, but nevertheless, the bug leads to assertion failures. This issue has been fixed by commit 8b178e6.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Quiclyto a version that resolves this vulnerability.Patch 8b178e6
Event History
Frequently Asked Questions
What is the severity of CVE-2026-44436?
CVE-2026-44436 has a severity score of 7.5, classified as high.
How does CVE-2026-44436 affect connection state in Quicly?
CVE-2026-44436 allows for connection state corruption, leading to potential Denial of Service.
What is the impact of exploiting CVE-2026-44436?
Exploitation of CVE-2026-44436 can result in a Denial of Service condition.
What versions of Quicly are affected by CVE-2026-44436?
CVE-2026-44436 affects Quicly prior to commit 8b178e6.
How do I remediate CVE-2026-44436?
To fix CVE-2026-44436, update Quicly to the version that includes commit 8b178e6.