{"answers":{"affected":"2 open source packages ship an affected version, including salvo. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33242 exists.","fix":"Upgrade salvo to 0.89.3 or later.","what":"CVE-2026-33242 is a high-severity path traversal vulnerability in salvo-rs salvo, published on 23 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-33242 and fix it if it is affected.\n\nWhat it is: CVE-2026-33242 is a high-severity path traversal vulnerability in salvo-rs salvo, published on 23 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33242 exists.\n\nAffected packages and fixed versions:\n- salvo (crates.io): affected from 0.39.0; fixed in 0.89.3\n- salvo (crates.io): affected from 0.39.0; fixed in 0.89.3\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-33242/ (Markdown: https://insights.sbomify.com/CVE-2026-33242/index.md)","id":"CVE-2026-33242","markdown":"https://insights.sbomify.com/CVE-2026-33242/index.md","name":"CVE-2026-33242","record":{"aliases":["GHSA-f842-phm9-p4v4"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust web framework","requires_auth":"none","summary":"An unauthenticated attacker can bypass proxy routing constraints to access protected backend endpoints due to improper path normalization in the Salvo framework.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"salvo","vendor":"salvo"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"Salvo is a Rust web framework. Versions 0.39.0 through 0.89.2 have a Path Traversal and Access Control Bypass vulnerability in the salvo-proxy component. The vulnerability allows an unauthenticated external attacker to bypass proxy routing constraints and access unintended backend paths (e.g., protected endpoints or administrative dashboards). This issue stems from the encode_url_path function, which fails to normalize \"../\" sequences and inadvertently forwards them verbatim to the upstream server by not re-encoding the \".\" character. Version 0.89.3 contains a patch.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Salvo has a Path Traversal in salvo-proxy::encode_url_path allows API Gateway Bypass","id":"CVE-2026-33242","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"barebox: FIT Signature Verification Bypass Vulnerability","id":"CVE-2026-33243"},"packages":[{"ecosystem":"crates.io","fixed":["0.89.3"],"introduced":["0.39.0"],"last_affected":[],"package":"salvo","purl":null,"source":"GHSA-f842-phm9-p4v4"},{"ecosystem":"crates.io","fixed":["0.89.3"],"introduced":["0.39.0"],"last_affected":[],"package":"salvo","purl":"pkg:cargo/salvo","source":"GHSA-f842-phm9-p4v4"}],"prev":{"headline":"Salvo Affected by Denial of Service via Unbounded Memory Allocation in Form Data Parsing","id":"CVE-2026-33241"},"products":["salvo"],"published":"2026-03-23","related":[{"cvss_score":8.8,"headline":"Salvo is vulnerable to reflected XSS in the list_html function","id":"CVE-2026-22256","kev_date_added":null,"published":"2026-01-08"},{"cvss_score":8.8,"headline":"Salvo is vulnerable to stored XSS in the list_html function by uploading files with malicious names","id":"CVE-2026-22257","kev_date_added":null,"published":"2026-01-08"},{"cvss_score":8.7,"headline":"Salvo Affected by Denial of Service via Unbounded Memory Allocation in Form Data Parsing","id":"CVE-2026-33241","kev_date_added":null,"published":"2026-03-23"}],"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":"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-24","vendors":["salvo-rs"]},"summary":"An unauthenticated attacker can bypass proxy routing constraints to access protected backend endpoints due to improper path normalization in the Salvo framework.","url":"https://insights.sbomify.com/CVE-2026-33242/"}