Public mode

No access to your tenant or devices. Every item links to its source. What this means

Some sources, documents or advisories need attention: 275/275 feeds/APIs · 469/469 docs · 8/9 advisories · checked 18:17 UTC Customize Public modeDiscuss ChangeIntel on Discord

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

Exact source revision recorded 26 Oct 2026 11:36:11 UTC. It does not establish the source's current position. Latest evidence.

osv · RUSTSEC-2026-0388

Published

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, `[email protected]`). 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 approved for one host is served by a different virtual host on the upstream. Deployments that do not accept HTTP/2 from clients, or that do not use the request authority for security or caching decisions, are not affected. This flaw was corrected in commits 915590a91811877795531f6ba0927a3138b5cb4b and ffab8302d08d4292d1924eb8fe84647fd5cb8e76. Pingora now returns 400 Bad Request for HTTP/2 requests whose Host differs from `:authority`, that contain more than one Host, or whose authority contains userinfo, and keeps the upstream Host or `:authority` consistent with the request authority. Users should upgrade to Pingora >= 0.9.0. Note: Cloudflare CDN customers were unaffected, as internal Pingora services at Cloudflare do not have HTTP/2 clients.

Source published
20 Oct 2026 12:00:00 UTC
Source modified
26 Oct 2026 11:15:11 UTC
Observed here
26 Oct 2026 11:36:11 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS_V4 · 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

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 7 Nov 18:17 UTC · 275 of 275 readable · 274 fully read · documentation 469/469 current