{"answers":{"affected":"3 open source packages ship an affected version, including pingora-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-4366 in the wild and no public exploit code.","fix":"Upgrade pingora-core to 0.5.0 or later.","what":"CVE-2025-4366 is a high-severity vulnerability in cloudflare:pingora, published on 22 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-4366 and fix it if it is affected.\n\nWhat it is: CVE-2025-4366 is a high-severity vulnerability in cloudflare:pingora, published on 22 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-4366 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pingora-core (crates.io): affected all versions; fixed in 0.5.0\n- pingora-core (crates.io): affected all versions; fixed in 0.5.0\n- pingora-core (crates.io): affected from 0.0.0-0; fixed in 0.5.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-4366/ (Markdown: https://insights.sbomify.com/CVE-2025-4366/index.md)","id":"CVE-2025-4366","markdown":"https://insights.sbomify.com/CVE-2025-4366/index.md","name":"CVE-2025-4366","record":{"aliases":["GHSA-93c7-7xqw-w357","RUSTSEC-2025-0037"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Rust proxy library","requires_auth":"none","summary":"Attackers can smuggle requests and poison caches in Pingora proxying frameworks when caching is enabled, requiring a patch to mitigate.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cloudflare","cpe":[{"product":"pingora","vendor":"cloudflare"}],"cvss":{"score":7.4,"severity":"high","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"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.\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.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Request Smuggling Vulnerability in Pingora","id":"CVE-2025-4366","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"other","year":"2025"},"n_packages":3,"n_references":1,"next":{"headline":"Download Manager \u003c= 3.3.18 - Authenticated (Author+) Stored Cross-site Scripting via wpdm_user_dashboard Shortcode","id":"CVE-2025-4367"},"packages":[{"ecosystem":"crates.io","fixed":["0.5.0"],"introduced":["0"],"last_affected":[],"package":"pingora-core","purl":null,"source":"GHSA-93c7-7xqw-w357"},{"ecosystem":"crates.io","fixed":["0.5.0"],"introduced":["0"],"last_affected":[],"package":"pingora-core","purl":"pkg:cargo/pingora-core","source":"GHSA-93c7-7xqw-w357"},{"ecosystem":"crates.io","fixed":["0.5.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"pingora-core","purl":"pkg:cargo/pingora-core","source":"RUSTSEC-2025-0037"}],"prev":{"headline":"NetScaler Console and NetScaler SDX (SVM) - Arbitrary file read","id":"CVE-2025-4365"},"products":["cloudflare:pingora"],"published":"2025-05-22","related":[{"cvss_score":9.3,"headline":"HTTP Request Smuggling via Premature Upgrade","id":"CVE-2026-2833","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":9.3,"headline":"HTTP Request Smuggling via HTTP/1.0 and Transfer-Encoding Misparsing","id":"CVE-2026-2835","kev_date_added":null,"published":"2026-03-04"},{"cvss_score":8.4,"headline":"Cache poisoning via insecure-by-default cache key","id":"CVE-2026-2836","kev_date_added":null,"published":"2026-03-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-18","vendors":["cloudflare"]},"summary":"Attackers can smuggle requests and poison caches in Pingora proxying frameworks when caching is enabled, requiring a patch to mitigate.","url":"https://insights.sbomify.com/CVE-2025-4366/"}