CVE-2026-44434: Quicly is vulnerable to stateless reset injection
Quicly is an IETF QUIC protocol implementation intended primarily for use within the H2O HTTP server. Prior to commit dccf5d4, Quicly was vulnerable to stateless reset injection through lack of packet entry validation. The QUIC protocol is designed to withstand packet injection attacks, once the handshake is complete. Only packets that carry some secret patterns are considered as stateless resets. Quicly allows the peer to share up to 4 such patterns per connection. However, until now, it failed to determine which of the 4 slots that it uses to retain the secret patterns contains a valid entry. As the slots are zero-initialized, the failure meant that, unless the peer advertised 4 of such patterns, an all-zero pattern was treated as a stateless reset.In effect, this allowed an on-path attacker to reset QUIC connections governed by Quicly. This issue has been fixed by commit dccf5d4.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Quiclyto a version that resolves this vulnerability.Patch dccf5d4
Event History
Frequently Asked Questions
What is the severity of CVE-2026-44434?
The severity of CVE-2026-44434 is classified as medium with a score of 5.3.
How do I fix CVE-2026-44434?
To fix CVE-2026-44434, update Quicly to the latest version that includes the commit dccf5d4 or later.
What is the impact of CVE-2026-44434?
CVE-2026-44434 can allow stateless reset injection due to insufficient packet entry validation.
Which software is affected by CVE-2026-44434?
CVE-2026-44434 affects the IETF Quicly implementation primarily used in the H2O HTTP server.
When was CVE-2026-44434 published?
CVE-2026-44434 was published on July 16, 2026.