--- title: "CVE-2026-105299: Pingora - Broken Access Control" description: "Pingora before 0.9.0 contains an HTTP header injection caused by improper removal of Connection and hop-by-hop headers in upstream_request_filter, letting remote attackers bypass IP-based authorization by removing trusted headers, exploit requires chained HTTP/1 intermediary deployment." url: https://panop.io/threat-heartbeat/CVE-2026-105299/ --- # CVE-2026-105299 Pingora - Broken Access Control Pingora before 0.9.0 contains an HTTP header injection caused by improper removal of Connection and hop-by-hop headers in upstream\_request\_filter, letting remote attackers bypass IP-based authorization by removing trusted headers, exploit requires chained HTTP/1 intermediary deployment. CVSS base score 8.7 /10 High CISA KEV Not listed Public exploit None known [View the NVD record ↗](https://nvd.nist.gov/vuln/detail/CVE-2026-105299) ## Details Type Broken Access Control Impact Broken Access Control CVSS vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N Published 20 October 2026 Updated 20 October 2026 ## Vendor fix Upgrade to Pingora version 0.9.0 or later; alternatively, remove Connection and nominated headers in upstream\_request\_filter before adding trusted headers. Patching closes this CVE. It does not tell you which of your systems run the affected version, or what else is exposed alongside them. ## References - [https://nvd.nist.gov/vuln/detail/CVE-2026-105299](https://nvd.nist.gov/vuln/detail/CVE-2026-105299) - [https://github.com/cloudflare/pingora](https://github.com/cloudflare/pingora) [← All CVEs](https://panop.io/threat-heartbeat/) ## What this record can't tell you - Whether you run the affected software, and where - Whether an attacker can actually reach and exploit it - The misconfigurations that never get a CVE number - What it would cost the business, ranked into what to fix first Panop answers these inside your environment, for this CVE and every other finding. [Book a demo](https://panop.io/demo)