dbcve.org
PingoraApplication · Cloudflare

CVE-2025-4366

MEDIUM · 6.1 CVSS v3.1 Published 2025-05-22
Fix available
A fix is available. Upgrade to 0.5.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A request smuggling vulnerability exists in Pingora's pingora-proxy caching framework where malicious HTTP requests can be injected via manipulated request bodies during cache HIT scenarios. This allows attackers to poison the cache and manipulate headers/URLs of subsequent requests on the same HTTP/1.1 connection.

MitigationApply the security patch from commit fda3317ec822678564d641e7cf1c9b77ee3759ff to fix the request smuggling issue in pingora-proxy, and validate that cache behavior is correct after the update.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PingoraApplication
Affected:< 0.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Pingora version
    Run 'cargo list pingora' or check your dependency lock file for the pingora crate version. If using a packaged version, check the package version metadata.
    Affected if The installed version is less than 0.5.0
  2. Identify if pingora-proxy is in use
    Review your application code and configuration for use of the pingora::proxy::ProxyHttp trait implementation. Search for 'use pingora::proxy' or 'impl ProxyHttp' in your codebase.
    Affected if pingora-proxy is being used as the reverse proxy framework
  3. Verify caching is enabled in proxy configuration
    Inspect your proxy configuration for cache-related settings, such as use of pingora's cache middleware or response caching flags. Check for 'cache' or 'Cache' in your configuration and code.
    Affected if Response caching is enabled in the proxy setup
  4. Confirm HTTP/1.1 connection reuse
    Check if your Pingora server is configured to handle HTTP/1.1 connections with keep-alive enabled, which allows connection reuse between multiple requests.
    Affected if HTTP/1.1 with keep-alive is enabled, allowing multiple requests on the same connection

You are affected if running Pingora version below 0.5.0 AND using pingora-proxy with response caching enabled AND serving HTTP/1.1 clients.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.5.0 or later
Fixed in 0.5.0
Interim mitigation

Apply the security patch from commit fda3317ec822678564d641e7cf1c9b77ee3759ff to fix the request smuggling issue in pingora-proxy, and validate that cache behavior is correct after the update.

Recommended fix High confidence

Pingora version 0.5.0 or later

  1. 1. Identify the current version of Pingora being used in your environment by checking your dependencies or running `cargo list | grep pingora` if using Cargo/Rust
  2. 2. Upgrade Pingora to version 0.5.0 or later by updating your Cargo.toml dependency: change `pingora = "<0.5.0"` to `pingora = "0.5.0"` or use a more recent stable version
  3. 3. Run `cargo update pingora` to fetch the new version
  4. 4. Rebuild and redeploy your Pingora-based services
  5. 5. Verify that the proxy caching functionality works correctly after the upgrade
  6. 6. Test for any regressions in request handling, especially with HTTP/1.1 connections and cached responses
Caveat Review the Pingora 0.5.0 release notes for any breaking changes related to proxy, caching, or HTTP/1.1 handling

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pingora Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4366 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-4366 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data