CVE-2025-4366
Last modified
CVE-2025-4366 is a medium-severity vulnerability rated 6.1/10 on the CVSS scale. 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.. EPSS estimates a 0.40% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Cloudflare | Pingora | < 0.5.0 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-4366?
How severe is CVE-2025-4366?
How do I fix CVE-2025-4366?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-4360A vulnerability, which was classified as critical, has been …9.8
- CVE-2025-4361A vulnerability classified as critical has been found in PHP…9.8
- CVE-2025-4362A vulnerability classified as critical was found in itsource…9.8
- CVE-2025-4363A vulnerability, which was classified as critical, has been …9.8
- CVE-2025-4364The affected products could allow an unauthenticated attacke…8.7
- CVE-2025-4365Arbitrary file read in NetScaler Console and NetScaler SDX (…7.5
- CVE-2025-4367The Download Manager plugin for WordPress is vulnerable to S…5.4
- CVE-2025-4368A vulnerability, which was classified as critical, was found…9.8
- CVE-2025-4369The Companion Auto Update plugin for WordPress is vulnerable…5.5
- CVE-2025-43697Improper Preservation of Permissions vulnerability in Salesf…7.5
- CVE-2025-43698Improper Preservation of Permissions vulnerability in Salesf…9.1
- CVE-2025-43699Client-Side Enforcement of Server-Side Security vulnerabilit…5.3
Are you affected by CVE-2025-4366?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST