CVE-2026-105299
waiting for further signalsZero needs more public information before it can validate it.GHSA-r9g2-75m7-w9wg ↗EUVD-2026-104781 ↗
description
Pingora before 0.9.0 can forward client-nominated Connection headers and related hop-by-hop headers on HTTP/1 upstream requests. An unauthenticated remote client may cause headers added by Pingora, such as trusted forwarding headers, to be removed and potentially bypass origin authorization when traffic passes through a downstream HTTP/1 intermediary that honors those headers.
mitigation
Upgrade Pingora to 0.9.0 or later and do not use HttpUpstreamRequestPolicy::preserve() where origins rely on headers added by Pingora. If upgrading is not immediately possible, remove the Connection header and every header it nominates before adding trusted headers in upstream_request_filter.
fixed in 0.9.0
outcome
No artifact: an exploit or check was attempted but could not be produced at this moment.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-20 01:07Zcve_org: trigger signal, started the run
this entry in the feed
GET /api/v1/feed/CVE-2026-105299
{ "etk_id": "ETK-2026-2113", "cve_id": "CVE-2026-105299", "display_id": "CVE-2026-105299", "ghsa_id": "GHSA-r9g2-75m7-w9wg", "euvd_id": "EUVD-2026-104781", "status": "published", "anchor_state": "anchored", "title": "HTTP/1 hop-by-hop header handling flaw in Pingora", "summary": "Pingora before 0.9.0 can forward client-nominated Connection headers and related hop-by-hop headers on HTTP/1 upstream requests. An unauthenticated remote client may cause headers added by Pingora, such as trusted forwarding headers, to be removed and potentially bypass origin authorization when traffic passes through a downstream HTTP/1 intermediary that honors those headers.", "mitigation": "Upgrade Pingora to 0.9.0 or later and do not use HttpUpstreamRequestPolicy::preserve() where origins rely on headers added by Pingora. If upgrading is not immediately possible, remove the Connection header and every header it nominates before adding trusted headers in upstream_request_filter.", "vendor": "Cloudflare", "product": "https://github.com/cloudflare/pingora", "affected": [ { "affected_notes": [], "affected_ranges": [ ">= 0.1.0, < 0.9.0" ], "ecosystem": null, "fixed_versions": [ "0.9.0" ], "package_name": "https://github.com/cloudflare/pingora", "purl": null } ], "cwes": null, "cvss_score": 8.7, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N", "epss_score": 0.0034, "epss_percentile": 0.2547, "epss_asof": "2026-10-20", "automation": "deterministic", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 22.718683283333334, "t0_at": "2026-10-20T01:07:12.767000+00:00", "signals": { "trigger_signal": { "at": "2026-10-20T01:07:12.767000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-20T01:07:12.767000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-105299" } } }
published 2026-10-20 02:11Z
last change 2026-10-21 10:15Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.