CVE-2026-44434

Quicly is vulnerable to stateless reset injection

Published Jul 16, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Quicly is an IETF QUIC protocol implementation used within the H2O HTTP server. Prior to commit dccf5d4, Quicly could accept stateless reset packets sent by an on‑path attacker because it did not validate which of the four shared secret patterns is active. QUIC expects reset packets to contain a secret pattern that only the communicating peers know; Quicly stores up to four such patterns, but failed to track which slot held a legitimate entry. As the unused slots are zero‑initialized, an all‑zero pattern was incorrectly treated as a valid stateless reset unless the peer advertised four patterns. This flaw allowed an attacker able to inject packets into an established QUIC session to reset the connection, effectively causing a denial‑of‑service.

Affected Systems

The vulnerability resides in the h2o:quicly implementation of the QUIC protocol. Versions of Quicly before the commit with SHA dccf5d4579c7ae9dd6e8f90c36d52e311bb60710 contain the flaw. Quicly allows a peer to share up to four stateless reset patterns per connection, but it fails to validate which slot contains a legitimate entry, leading to zero‑initialized slots being treated as stateless resets. The patch introduces proper slot validation to prevent the misuse of zero‑initialized entries.

Risk and Exploitability

The CVSS score of 5.3 places the issue in the moderate range, while the EPSS score of less than 1% indicates a very low exploitation probability under current conditions. It is not listed in the CISA KEV catalog. An attacker who can intercept or inject traffic on a QUIC connection can exploit this flaw by sending an all‑zero stateless reset, causing the server to close the session prematurely. The weakness does not require prior authentication or privileged access, but does rely on the ability to send packets to the target connection.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Quicly to a release that includes commit dccf5d4579c7ae9dd6e8f90c36d52e311bb60710.
  • Rebuild or redeploy the H2O HTTP server using the updated Quicly library.
  • Monitor QUIC session stability following the update to confirm that no arbitrary resets occur.

Generated by OpenCVE AI on July 31, 2026 at 01:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared H2o
H2o quicly
Vendors & Products H2o
H2o quicly
Type Values Removed Values Added
Description 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.
Title Quicly is vulnerable to stateless reset injection
Weaknesses CWE-345
CWE-665
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

  • CWE-665

    Improper Initialization

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 18, 2026, 3:21 AM
Reserved
May 6, 2026, 2:40 PM
Status
Analyzed
Published
Jul 16, 2026, 11:16 PM
Modified
Oct 24, 2026, 8:10 PM