{"id":"CVE-2025-4366","published":"2025-05-22T15:50:20Z","modified":"2025-06-18T13:46:25Z","title":"Request Smuggling Vulnerability in Pingora","vendor":null,"product":null,"tier":"tail","description":{"text":"A request smuggling vulnerability identified within Pingora’s proxying framework, pingora-proxy, allows malicious HTTP requests to be injected via manipulated request bodies on cache HITs, leading to unauthorized request execution and potential cache poisoning.\n\nFixed in:  https://github.com/cloudflare/pingora/commit/fda3317ec822678564d641e7cf1c9b77ee3759ff https://github.com/cloudflare/pingora/commit/fda3317ec822678564d641e7cf1c9b77ee3759ff \n\nImpact: The issue could lead to request smuggling in cases where Pingora’s proxying framework, pingora-proxy, is used for caching allowing an attacker to manipulate headers and URLs in subsequent requests made on the same HTTP/1.1 connection.","provenance":"source","from":"CVE.org"},"cvss":{"score":7.4,"severity":"HIGH","version":"4.0","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:A/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N","provenance":"source","from":"CVE.org CNA"},"epss":{"score":0.00545,"percentile":0.46649,"provenance":"source"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"references":[{"url":"https://github.com/cloudflare/pingora","tags":[]}],"priority":{"score":14.5,"factors":[{"name":"EPSS percentile","points":9.33},{"name":"CVSS severity","points":5.18}]},"affectedVersions":[{"vendor":null,"product":null,"versions":["< 0.5.0"]}],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"partial","timestamp":"2025-05-22T18:30:25.819289Z","from":"CISA ADP","provenance":"source"},"affected":[{"ecosystem":"crates.io","package":"pingora-core","vulnerableRanges":["<0.5.0",">=0.0.0-0, <0.5.0"],"patched":["0.5.0"],"from":["GHSA-93c7-7xqw-w357","RUSTSEC-2025-0037"],"provenance":"source"}],"summary":{"text":"A request smuggling flaw in the pingora-proxy component of Cloudflare's Pingora proxying framework lets malicious HTTP requests be injected through manipulated request bodies on cache hits. An attacker can use this to smuggle requests that alter headers and URLs in subsequent requests on the same HTTP/1.1 connection, which can lead to unauthorized request execution and potential cache poisoning, though the attack depends on Pingora being used as a caching proxy and requires the attacker to send crafted requests over the network.","provenance":"ai","model":"claude-haiku-5-5","generatedAt":"2026-11-20T21:35:11Z"},"euvd":{"id":"EUVD-2025-16165","exploited":false,"provenance":"source"}}