Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-vx4q-2c55-cvmg

Pingora forwards client-nominated Connection headers to HTTP/1 upstreams, allowing ACL bypass in specific chained deployments

CVSS 8.7 HighEPSS 0.0043 · 36th percentile

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.

PackageEcosystemAffectedFixed in
pingora-proxycrates.io>=0.0.0-0, <0.9.00.9.0
Identifiers
GHSA-vx4q-2c55-cvmg · CVE-2026-105299 · RUSTSEC-2026-0390
Weakness (CWE)
CWE-444
Tags
Published
20 Oct 2026
Updated
26 Oct 2026

Machine-written summary

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

Pingora (crates.io package pingora-proxy) versions before 0.9.0 forward the client's Connection header and the headers it names to HTTP/1 upstreams without removing them. A remote, unauthenticated attacker can exploit this in chained deployments where an HTTP/1 intermediary honors Connection and the origin trusts headers that Pingora adds, such as X-Forwarded-For, potentially bypassing IP-based authorization. Upgrade to pingora-proxy 0.9.0, which removes hop-by-hop and Connection-nominated headers by default; the source gives no other workaround.

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

ScoreRatingCVSSVectorSource
8.7 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N CNA (cloudflare)
  • CISA KEV Not listed.
  • EPSS 0.0043, the 36th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:24 UTC First seen by agentprime
  2. 31 Oct 2026, 14:24 UTC Confirmed by OSV

Sources

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.