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.
Fixed in: https://github.com/cloudflare/pingora/commit/fda3317ec822678564d641e7cf1c9b77ee3759ff https://github.com/cloudflare/pingora/commit/fda3317ec822678564d641e7cf1c9b77ee3759ff
Impact: 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.
References
| Link | Resource |
|---|---|
| https://github.com/cloudflare/pingora | Product |
Configurations
History
06 Aug 2025, 17:01
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:cloudflare:pingora:*:*:*:*:*:*:*:* | |
| CVSS |
v2 : v3 : |
v2 : unknown
v3 : 6.1 |
| References | () https://github.com/cloudflare/pingora - Product | |
| First Time |
Cloudflare pingora
Cloudflare |
22 May 2025, 16:15
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2025-05-22 16:15
Updated : 2025-08-06 17:01
NVD link : CVE-2025-4366
Mitre link : CVE-2025-4366
JSON object : View
Products Affected
cloudflare
- pingora
CWE
No CWE.