{"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-2026-2833 in the wild and no public exploit code.","fix":"Upgrade pingora-core to 0.8.0 or later.","what":"CVE-2026-2833 is a critical vulnerability in https://github.com/cloudflare/pingora, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-2833 and fix it if it is affected.\n\nWhat it is: CVE-2026-2833 is a critical vulnerability in https://github.com/cloudflare/pingora, published on 4 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-2833 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.8.0\n- pingora-core (crates.io): affected all versions; fixed in 0.8.0\n- pingora-core (crates.io): affected from 0.0.0-0; fixed in 0.8.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-2026-2833/ (Markdown: https://insights.sbomify.com/CVE-2026-2833/index.md)","id":"CVE-2026-2833","markdown":"https://insights.sbomify.com/CVE-2026-2833/index.md","name":"CVE-2026-2833","record":{"aliases":["GHSA-xq2h-p299-vjwv","RUSTSEC-2026-0033"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Pingora proxy library","requires_auth":"none","summary":"Attackers can smuggle HTTP requests via premature upgrade handling to bypass security controls and hijack user sessions in Pingora proxies.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cloudflare","cpe":[{"product":"pingora","vendor":"cloudflare"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-444","name":"Inconsistent Interpretation of HTTP Requests"}],"description":"An HTTP request smuggling vulnerability (CWE-444) was found in Pingora's handling of HTTP/1.1 connection upgrades. The issue occurs when a Pingora proxy reads a request containing an Upgrade header, causing the proxy to pass through the rest of the bytes on the connection to a backend before the backend has accepted the upgrade. An attacker can thus directly forward a malicious payload after a request with an Upgrade header to that backend in a way that may be interpreted as a subsequent request header, bypassing proxy-level security controls and enabling cross-user session hijacking.\n\nImpact\n\nThis vulnerability primarily affects standalone Pingora deployments where a Pingora proxy is exposed to external traffic. An attacker could exploit this to:\n\n  *  Bypass proxy-level ACL controls and WAF logic\n\n  *  Poison caches and upstream connections, causing subsequent requests from legitimate users to receive responses intended for smuggled requests\n\n  *  Perform cross-user attacks by hijacking sessions or smuggling requests that appear to originate from the trusted proxy IP\n\nCloudflare's CDN infrastructure was not affected by this vulnerability, as ingress proxies in the CDN stack maintain proper HTTP parsing boundaries and do not prematurely switch to upgraded connection forwarding mode.\n\nMitigation:\n\nPingora users should upgrade to Pingora v0.8.0 or higher\n\nAs a workaround, users may return an error on requests with the Upgrade header present in their request filter logic in order to stop processing bytes beyond the request header and disable downstream connection reuse.","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":"HTTP Request Smuggling via Premature Upgrade","id":"CVE-2026-2833","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"other","year":"2026"},"n_packages":3,"n_references":1,"next":{"headline":"Cross-site scripting in Age Verification \u0026 Identity Verification by Token of Trust","id":"CVE-2026-2834"},"packages":[{"ecosystem":"crates.io","fixed":["0.8.0"],"introduced":["0"],"last_affected":[],"package":"pingora-core","purl":null,"source":"GHSA-xq2h-p299-vjwv"},{"ecosystem":"crates.io","fixed":["0.8.0"],"introduced":["0"],"last_affected":[],"package":"pingora-core","purl":"pkg:cargo/pingora-core","source":"GHSA-xq2h-p299-vjwv"},{"ecosystem":"crates.io","fixed":["0.8.0"],"introduced":["0.0.0-0"],"last_affected":[],"package":"pingora-core","purl":"pkg:cargo/pingora-core","source":"RUSTSEC-2026-0033"}],"prev":{"headline":"Certain Samsung MultiXpress Multifunction Printers Firmware – Potential Information Disclosure","id":"CVE-2026-2832"},"products":["https://github.com/cloudflare/pingora"],"published":"2026-03-04","related":[{"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"},{"cvss_score":7.4,"headline":"Request Smuggling Vulnerability in Pingora","id":"CVE-2025-4366","kev_date_added":null,"published":"2025-05-22"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-06","vendors":["Cloudflare"]},"summary":"Attackers can smuggle HTTP requests via premature upgrade handling to bypass security controls and hijack user sessions in Pingora proxies.","url":"https://insights.sbomify.com/CVE-2026-2833/"}