{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-40024 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-40024 is a high-severity path traversal vulnerability in sleuthkit, published on 8 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-40024 and fix it if it is affected.\n\nWhat it is: CVE-2026-40024 is a high-severity path traversal vulnerability in sleuthkit, published on 8 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-40024 in the wild and no public exploit code.\n\nAffected product: sleuthkit. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-40024/ (Markdown: https://insights.sbomify.com/CVE-2026-40024/index.md)","id":"CVE-2026-40024","markdown":"https://insights.sbomify.com/CVE-2026-40024/index.md","name":"CVE-2026-40024","record":{"aliases":["AZL-82007","DEBIAN-CVE-2026-40024","GHSA-995r-jc2c-558w","UBUNTU-CVE-2026-40024"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Digital forensics library","requires_auth":"none","summary":"Attackers can write files to arbitrary locations via crafted filesystem images, potentially achieving code execution by overwriting system configurations.","user_interaction":"required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"the_sleuth_kit","vendor":"sleuthkit"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/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 Sleuth Kit through 4.14.0 contains a path traversal vulnerability in tsk_recover that allows an attacker to write files to arbitrary locations outside the intended recovery directory via crafted filenames or directory paths with path traversal sequences in a filesystem image. An attacker can craft a malicious filesystem image with embedded /../ sequences in filenames that, when processed by tsk_recover, writes files outside the output directory, potentially achieving code execution by overwriting shell configuration or cron entries.","ecosystems":[],"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":"Sleuth Kit tsk_recover Path Traversal","id":"CVE-2026-40024","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Sleuth Kit APFS Keybag Parser Out-of-Bounds Read","id":"CVE-2026-40025"},"packages":[],"prev":{"headline":"Other in Apache Log4cxx","id":"CVE-2026-40023"},"products":["sleuthkit"],"published":"2026-04-08","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2019-14531","kev_date_added":null,"published":"2019-08-02"},{"cvss_score":9.1,"headline":"Memory corruption in n/a","id":"CVE-2020-10233","kev_date_added":null,"published":"2020-03-08"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2018-11737","kev_date_added":null,"published":"2018-06-05"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2018-11738","kev_date_added":null,"published":"2018-06-05"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2018-11739","kev_date_added":null,"published":"2018-06-05"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2018-11740","kev_date_added":null,"published":"2018-06-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"2026-10-01","vendors":["sleuthkit"]},"summary":"Attackers can write files to arbitrary locations via crafted filesystem images, potentially achieving code execution by overwriting system configurations.","url":"https://insights.sbomify.com/CVE-2026-40024/"}