Process crash via invalid QUIC frame handling
Published Jan 19, 2026 · Updated Jan 19, 2026
Improper input validation in H2O quicly before commit d9d3df6 allows remote attackers to crash its host process using invalid QUIC frames. Quicly's frame-processing path fails to reject certain invalid QUIC frames and instead reaches internal assertions that terminate the process. No authentication or user interaction is required; a shared process serving multiple QUIC connections drops innocent connections when it crashes.
Summary
What happened
Improper input validation in H2O quicly before commit d9d3df6 allows remote attackers to crash its host process using invalid QUIC frames. Quicly's frame-processing path fails to reject certain invalid QUIC frames and instead reaches internal assertions that terminate the process. No authentication or user interaction is required; a shared process serving multiple QUIC connections drops innocent connections when it crashes.
The record
- CVE
- CVE-2025-61684
- Published
- Jan 19, 2026
- Updated
- Jan 19, 2026
- Vendor
- H2O Project
- Product
- quicly
- Classifications
- CWE-617, CWE-20, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 19, 2026CVE publishedPublication date reported by the CVE source.
- Jan 19, 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=< d9d3df6
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