Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Versions of the Go package github.com/quic-go/quic-go before 0.42.0 are vulnerable to memory exhaustion. An attacker who can connect to a peer can send many NEW_CONNECTION_ID frames that retire old connection IDs, while manipulating the peer's congestion window and RTT estimate so that the peer sends few of the required RETIRE_CONNECTION_ID responses, causing the peer to run out of memory. Upgrade to version 0.42.0 or later; the source lists no workaround.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.011, the 66th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:15 UTC First seen by agentprime
- 31 Oct 2026, 14:15 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-c33x-xqrf-c478
- OSV: GHSA-c33x-xqrf-c478
- github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478
- nvd.nist.gov/vuln/detail/CVE-2024-22189
- github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c85ed47a
- github.com/quic-go/quic-go
- seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management
- www.youtube.com/watch?v=JqXtYcZAtIA&t=3683s