{"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-22256 exists.","fix":"Upgrade salvo to 0.88.1 or later.","what":"CVE-2026-22256 is a high-severity cross-site scripting vulnerability in salvo-rs salvo, published on 8 Jan 2026. 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-2026-22256 and fix it if it is affected.\n\nWhat it is: CVE-2026-22256 is a high-severity cross-site scripting vulnerability in salvo-rs salvo, published on 8 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-22256 exists.\n\nAffected packages and fixed versions:\n- salvo (crates.io): affected all versions; fixed in 0.88.1\n- salvo (crates.io): affected all versions; fixed in 0.88.1\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-22256/ (Markdown: https://insights.sbomify.com/CVE-2026-22256/index.md)","id":"CVE-2026-22256","markdown":"https://insights.sbomify.com/CVE-2026-22256/index.md","name":"CVE-2026-22256","record":{"aliases":["GHSA-rjf8-2wcw-f6mp"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust web framework","requires_auth":"none","summary":"Attackers can execute arbitrary scripts in victim browsers via reflected XSS in the Salvo Rust web framework's file listing feature.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"salvo","vendor":"salvo"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Salvo is a Rust web backend framework. Prior to version 0.88.1, the function list_html generate an file view of a folder which include a render of the current path, in which its inserted in the HTML without proper sanitation, this leads to reflected XSS using the fact that request path is decoded and normalized in the matching stage but not is inserted raw in the html view (current.path), the only constraint here is for the root path (eg. /files in the PoC example) to have a sub directory (e.g common ones styles/scripts/etc…) so that the matching return the list HTML page instead of the Not Found page. This issue has been patched in version 0.88.1.","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 is vulnerable to reflected XSS in the list_html function","id":"CVE-2026-22256","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"Salvo is vulnerable to stored XSS in the list_html function by uploading files with malicious names","id":"CVE-2026-22257"},"packages":[{"ecosystem":"crates.io","fixed":["0.88.1"],"introduced":["0"],"last_affected":[],"package":"salvo","purl":null,"source":"GHSA-rjf8-2wcw-f6mp"},{"ecosystem":"crates.io","fixed":["0.88.1"],"introduced":["0"],"last_affected":[],"package":"salvo","purl":"pkg:cargo/salvo","source":"GHSA-rjf8-2wcw-f6mp"}],"prev":{"headline":"iccDEV has heap-buffer-overflow in CIccCLUT::Init() at IccProfLib/IccTagLut.cpp","id":"CVE-2026-22255"},"products":["salvo"],"published":"2026-01-08","related":[{"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"},{"cvss_score":7.5,"headline":"Salvo has a Path Traversal in salvo-proxy::encode_url_path allows API Gateway Bypass","id":"CVE-2026-33242","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-08","vendors":["salvo-rs"]},"summary":"Attackers can execute arbitrary scripts in victim browsers via reflected XSS in the Salvo Rust web framework's file listing feature.","url":"https://insights.sbomify.com/CVE-2026-22256/"}