# QUIC's Connection ID Mechanism vulnerable to Memory Exhaustion Attack

Advisory record · `GHSA-c33x-xqrf-c478`

- **Identifiers:** `GHSA-c33x-xqrf-c478` · `CVE-2024-22189` · `GO-2024-2682`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html) · [CWE-770](https://cwe.mitre.org/data/definitions/770.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 2 Apr 2024
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 2 Apr 2024, 14:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/quic-go/quic-go` (Go): affected `<0.42.0`; fixed in `0.42.0`

## 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.

Written 2 Nov 2026.

## 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

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from 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](https://osv.dev/vulnerability/GHSA-c33x-xqrf-c478)

## Sources

- [GitHub Advisory Database: GHSA-c33x-xqrf-c478](https://github.com/advisories/GHSA-c33x-xqrf-c478)
- [OSV: GHSA-c33x-xqrf-c478](https://osv.dev/vulnerability/GHSA-c33x-xqrf-c478)
- <https://github.com/quic-go/quic-go/security/advisories/GHSA-c33x-xqrf-c478>
- <https://nvd.nist.gov/vuln/detail/CVE-2024-22189>
- <https://github.com/quic-go/quic-go/commit/4a99b816ae3ab03ae5449d15aac45147c85ed47a>
- <https://github.com/quic-go/quic-go>
- <https://seemann.io/posts/2024-03-19-exploiting-quics-connection-id-management>
- <https://www.youtube.com/watch?v=JqXtYcZAtIA&t=3683s>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-c33x-xqrf-c478>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-c33x-xqrf-c478/>. Everything for agents: <https://agentprime.io/llms.txt>.
