https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 09:48:20 +0000 https://cve.radiocsirt.org/vuln/cve-2026-2833 <p><strong>Affected:</strong> Cloudflare https://github.com/cloudflare/pingora</p> <p>An HTTP request smuggling vulnerability (CWE-444) was found in Pingora&#39;s handling of HTTP/1.1 connection upgrades. The issue occurs when a Pingora proxy reads a request containing an Upgrade header, causing the proxy to pass through the rest of the bytes on the connection to a backend before the backend has accepted the upgrade. An attacker can thus directly forward a malicious payload after a request with an Upgrade header to that backend in a way that may be interpreted as a subsequent request header, bypassing proxy-level security controls and enabling cross-user session hijacking.</p> <p>Impact</p> <p>This vulnerability primarily affects standalone Pingora deployments where a Pingora proxy is exposed to external traffic. An attacker could exploit this to:</p> <p>* Bypass proxy-level ACL controls and WAF logic</p> <p>* Poison caches and upstream connections, causing subsequent requests from legitimate users to receive responses intended for smuggled requests</p> <p>* Perform cross-user attacks by hijacking sessions or smuggling requests that appear to originate from the trusted proxy IP</p> <p>Cloudflare&#39;s CDN infrastructure was not affected by this vulnerability, as ingress proxies in the CDN stack maintain proper HTTP parsing boundaries and do not prematurely switch to upgraded connection forwarding mode.</p> <p>Mitigation:</p> <p>Pingora users should upgrade to Pingora v0.8.0 or higher</p> <p>As a workaround, users may return an error on requests with the Upgrade header present in their request filter…</p> <p><strong>Affected:</strong> Cloudflare https://github.com/cloudflare/pingora</p> <p>An HTTP request smuggling vulnerability (CWE-444) was found in Pingora&#39;s handling of HTTP/1.1 connection upgrades. The issue occurs when a Pingora proxy reads a request containing an Upgrade header, causing the proxy to pass through the rest of the bytes on the connection to a backend before the backend has accepted the upgrade. An attacker can thus directly forward a malicious payload after a request with an Upgrade header to that backend in a way that may be interpreted as a subsequent request header, bypassing proxy-level security controls and enabling cross-user session hijacking.</p> <p>Impact</p> <p>This vulnerability primarily affects standalone Pingora deployments where a Pingora proxy is exposed to external traffic. An attacker could exploit this to:</p> <p>* Bypass proxy-level ACL controls and WAF logic</p> <p>* Poison caches and upstream connections, causing subsequent requests from legitimate users to receive responses intended for smuggled requests</p> <p>* Perform cross-user attacks by hijacking sessions or smuggling requests that appear to originate from the trusted proxy IP</p> <p>Cloudflare&#39;s CDN infrastructure was not affected by this vulnerability, as ingress proxies in the CDN stack maintain proper HTTP parsing boundaries and do not prematurely switch to upgraded connection forwarding mode.</p> <p>Mitigation:</p> <p>Pingora users should upgrade to Pingora v0.8.0 or higher</p> <p>As a workaround, users may return an error on requests with the Upgrade header present in their request filter…</p> https://cve.radiocsirt.org/vuln/cve-2026-2833