# Pingora HTTP/2 :authority and Host header mismatch enables cache poisoning and host-based access control bypass

Advisory record · `GHSA-mgg9-6xw2-jfgp`

- **Identifiers:** `GHSA-mgg9-6xw2-jfgp` · `CVE-2026-105298` · `RUSTSEC-2026-0388`
- **State:** Confirmed
- **Severity:** CVSS 6.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-444](https://cwe.mitre.org/data/definitions/444.html)
- **Tags:** [HTTP request smuggling](https://agentprime.io/advisories/tag/request-smuggling.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.9.0`; fixed in `0.9.0`

## Machine-written summary

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

> Pingora (crates.io package pingora-core) versions before 0.9.0 accepted HTTP/2 requests whose Host header differed from the :authority value, so the application and the upstream could see different hosts. A remote, unauthenticated attacker can send one HTTP/2 request to cause cache poisoning or bypass host-based access control, where the upstream routes by Host. Upgrade to pingora-core 0.9.0 or later, which rejects such requests with 400 Bad Request.

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

- 6.3 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`, from CNA (cloudflare)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0056, the 46th percentile, on 5 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-0388)

## Sources

- [GitHub Advisory Database: GHSA-mgg9-6xw2-jfgp](https://github.com/advisories/GHSA-mgg9-6xw2-jfgp)
- [OSV: GHSA-mgg9-6xw2-jfgp](https://osv.dev/vulnerability/GHSA-mgg9-6xw2-jfgp)
- <https://crates.io/crates/pingora-core>
- <https://rustsec.org/advisories/RUSTSEC-2026-0388.html>
- <https://github.com/cloudflare/pingora/commit/915590a91811877795531f6ba0927a3138b5cb4b>
- <https://github.com/cloudflare/pingora/commit/ffab8302d08d4292d1924eb8fe84647fd5cb8e76>

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-mgg9-6xw2-jfgp>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-mgg9-6xw2-jfgp/>. Everything for agents: <https://agentprime.io/llms.txt>.