Quicly has assertion failures
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-617.
Summary
Quicly, an IETF QUIC protocol implementation, is susceptible to a denial-of-service attack prior to commit d9d3df6a8530a102b57d840e39b0311ce5c9e14e. A remote attacker can exploit these bugs to trigger an assertion failure that crashes process using Quicly. Commit d9d3df6a8530a102b57d840e39b0311ce5c9e14e fixes the issue.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2025-61684
References
More h2oai Quicly vulnerabilities
- TI-2026-32377 Quicly is vulnerable to connection state corruption CVSS 3.1HIGH 7.5
- TI-2026-32376 Quicly: Remote Denial of Service via assertion failure when CRYPTO stream handshake data exceeds 32KB CVSS 3.1HIGH 7.5
- TI-2026-32374 Quicly is vulnerable to memory exhaustion CVSS 3.1HIGH 7.5
- TI-2026-32375 Quicly is vulnerable to stateless reset injection CVSS 3.1MEDIUM 5.3
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences