# Pingora HTTP/2 server memory exhaustion through unbounded default header-list and concurrent-stream limits

Advisory record · `GHSA-7gpj-mj4q-x62x`

- **Identifiers:** `GHSA-7gpj-mj4q-x62x` · `CVE-2026-105297` · `RUSTSEC-2026-0389`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-770](https://cwe.mitre.org/data/definitions/770.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 20 Oct 2026
- **Updated:** 26 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 20 Oct 2026, 12:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `pingora-core` (crates.io): affected `>=0.0.0-0, <0.8.1`; fixed in `0.8.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Pingora (crates.io pingora-core) versions before 0.8.1 are affected when HTTP/2 server limits are left at the h2 crate defaults, which means no limit on concurrent streams and a 16 MiB header-list size. A remote, unauthenticated client can open many streams on one connection with small header data and keep them open via flow control, exhausting server memory and possibly terminating the process. Upgrade to pingora-core 0.8.1 or later. If your application supplies its own H2Options, set max_header_list_size and max_concurrent_streams explicitly, since the new defaults do not apply to them.

Written 3 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 (cloudflare)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0043, the 37th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:24 UTC: First seen by agentprime
- 31 Oct 2026, 14:24 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/RUSTSEC-2026-0389)

## Sources

- [GitHub Advisory Database: GHSA-7gpj-mj4q-x62x](https://github.com/advisories/GHSA-7gpj-mj4q-x62x)
- [OSV: GHSA-7gpj-mj4q-x62x](https://osv.dev/vulnerability/GHSA-7gpj-mj4q-x62x)
- <https://crates.io/crates/pingora-core>
- <https://rustsec.org/advisories/RUSTSEC-2026-0389.html>
- <https://github.com/cloudflare/pingora/commit/d193c8d49b8b7c1c1ede93183759caa4f6906bbd>

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-7gpj-mj4q-x62x>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-7gpj-mj4q-x62x/>. Everything for agents: <https://agentprime.io/llms.txt>.