CVE-2025-4366

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in, but needs a user to act. High risk of data exposure, data tampering.

Exploit odds

0.5% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2025-05-22 16:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 09:33 UTC Last updatedMost recent change to the record

Details

Published

2025-05-22 16:15 UTC

Last modified

2026-06-17 09:33 UTC

Exploit probability

0.5% · EPSS, next 30 days

Weakness

CWE-444

Record status

Analyzed

Affected

• Cloudflare Pingora < 0.5.0

Attack profile CVSS 4.0 · 7.4

Attack vector

Network

Complexity

High

Attack requirements

Present

Privileges needed

None

User interaction

Active

Confidentiality

High

Integrity

High

Availability

None