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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.3 · 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 · score source

EPSS

• CVE-2026-105298: 0.56% estimated exploitation activity in the next 30 days; percentile 46.54 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Pingora versions prior to 0.9.0 accepted HTTP/2 requests whose Host header differed from the `:authority` pseudo-header. Request filters, cache keys, and logs that read the request URI (`session.req_header().uri`) saw the `:authority` value, but the upstream received the client-supplied Host value. Pingora also accepted `:authority` values containing userinfo (for example, `user@example.com`). This violates RFC 9113 Section 8.3.1, which requires an intermediary to use the `:authority` value for Host and replace any existing Host field. A remote, unauthenticated attacker can send a single HTTP/2 request that the application sees as one host and the upstream receives as another. Where request filters, access controls, or cache keys use the URI authority and the upstream routes by Host, this can lead to cache poisoning, where a response from another virtual host is stored under the victim host's cache key and served to other users, or host-based access control bypass, where a request…

Published by the source

20 Oct 2026, 12:00 UTC

Last modified by the source

26 Oct 2026, 11:15 UTC

Source last checked

26 Oct 2026, 12:45 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from osv record RUSTSEC-2026-0388

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-105298

Advisory: Pingora HTTP/2 :authority and Host header mismatch enables cache poisoning and host-based access control bypass
IDs: CVE-2026-105298, GHSA-mgg9-6xw2-jfgp
Record: https://patchnext.com/advisories/cve-2026-105298 (revision 1, source checked 26 Oct 2026, 12:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pingora-core 0.9.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io pingora-core: affected >= 0.0.0-0, < 0.9.0; fixed in 0.9.0

## Suggested inspection (read-only)
- crates.io pingora-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pingora-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/RUSTSEC-2026-0388 (OSV record RUSTSEC-2026-0388 lists affected ranges: crates.io pingora-core >=0.0.0-0 <0.9.0 (fixed))

Commands are suggestions: review each one before running it.