Remote service crash via CRYPTO stream assertion
Published Jul 16, 2026 · Updated Jul 16, 2026
Reachable assertion in H2O quicly before commit 937d0e9 allows remote attackers to crash a QUIC endpoint with oversized handshake data. The receive path applies stream flow-control update logic to an internal negative CRYPTO stream ID after valid handshake data crosses the threshold, reaching an assertion. No authentication or user interaction is required; the result is service interruption without reported data disclosure or modification.
Summary
What happened
Reachable assertion in H2O quicly before commit 937d0e9 allows remote attackers to crash a QUIC endpoint with oversized handshake data. The receive path applies stream flow-control update logic to an internal negative CRYPTO stream ID after valid handshake data crosses the threshold, reaching an assertion. No authentication or user interaction is required; the result is service interruption without reported data disclosure or modification.
The record
- CVE
- CVE-2026-44435
- Published
- Jul 16, 2026
- Updated
- Jul 16, 2026
- Vendor
- H2O Project
- Product
- quicly
- Classifications
- CWE-400, CWE-617, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 16, 2026CVE publishedPublication date reported by the CVE source.
- Jul 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 937d0e9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo