{"answers":{"affected":"2 open source packages ship an affected version, including actix-files.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-72814 exists.","fix":"Upgrade actix-files to 0.6.10 or later.","what":"CVE-2026-72814 is a medium-severity path traversal vulnerability in actix-files, published on 14 Aug 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-72814 and fix it if it is affected.\n\nWhat it is: CVE-2026-72814 is a medium-severity path traversal vulnerability in actix-files, published on 14 Aug 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-72814 exists.\n\nAffected packages and fixed versions:\n- actix-files (crates.io): affected all versions; fixed in 0.6.10\n- actix-files (crates.io): affected all versions; fixed in 0.6.10\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-72814/ (Markdown: https://insights.sbomify.com/CVE-2026-72814/index.md)","id":"CVE-2026-72814","markdown":"https://insights.sbomify.com/CVE-2026-72814/index.md","name":"CVE-2026-72814","record":{"aliases":["CLEANSTART-2026-QW59159","GHSA-8v2v-wjwg-vx6r","GHSA-f87p-3w4v-5q9x","UBUNTU-CVE-2026-72814"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Rust web framework","requires_auth":"none","summary":"Attackers can access unintended files by exploiting path resolution flaws when serving from non-existent folders in actix-files.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"The actix-files crate (actix_files) before version 0.6.10 contains an information exposure vulnerability. When a non-existing folder is passed as the serve_from argument to Files::new(), the mount path defaults to an empty path; the service then joins the request path with this empty path and canonicalizes it, causing Rust to resolve it as a relative path. As a result, an attacker can request paths that resolve relative to the application's working directory and access unintended files.","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":"actix-files before 0.6.10 Information Disclosure via Files","id":"CVE-2026-72814","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"go-chi chi v5.2.1 IP Spoofing via X-Forwarded-For Header","id":"CVE-2026-72815"},"packages":[{"ecosystem":"crates.io","fixed":["0.6.10"],"introduced":["0"],"last_affected":[],"package":"actix-files","purl":null,"source":"GHSA-8v2v-wjwg-vx6r"},{"ecosystem":"crates.io","fixed":["0.6.10"],"introduced":["0"],"last_affected":[],"package":"actix-files","purl":"pkg:cargo/actix-files","source":"GHSA-8v2v-wjwg-vx6r"}],"prev":{"headline":"actix-files before 0.6.10 Denial of Service via empty Range header","id":"CVE-2026-72813"},"products":["actix-files"],"published":"2026-08-14","related":[],"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":"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-10-29","vendors":["actix"]},"summary":"Attackers can access unintended files by exploiting path resolution flaws when serving from non-existent folders in actix-files.","url":"https://insights.sbomify.com/CVE-2026-72814/"}