{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-40025 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-40025 is a medium-severity 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-40025 and fix it if it is affected.\n\nWhat it is: CVE-2026-40025 is a medium-severity 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-40025 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-40025/ (Markdown: https://insights.sbomify.com/CVE-2026-40025/index.md)","id":"CVE-2026-40025","markdown":"https://insights.sbomify.com/CVE-2026-40025/index.md","name":"CVE-2026-40025","record":{"aliases":["AZL-82004","DEBIAN-CVE-2026-40025","GHSA-fhjv-wmq6-3c5h","UBUNTU-CVE-2026-40025"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Digital forensics library","requires_auth":"none","summary":"An attacker can craft a malicious APFS disk image to trigger an out-of-bounds read in Sleuth Kit, leading to information disclosure or application crashes.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"the_sleuth_kit","vendor":"sleuthkit"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"The Sleuth Kit through 4.14.0 contains an out-of-bounds read vulnerability in the APFS filesystem keybag parser where the wrapped_key_parser class follows attacker-controlled length fields without bounds checking, causing heap reads past the allocated buffer. An attacker can craft a malicious APFS disk image that triggers information disclosure or crashes when processed by any Sleuth Kit tool that parses APFS volumes.","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 APFS Keybag Parser Out-of-Bounds Read","id":"CVE-2026-40025","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Sleuth Kit ISO9660 SUSP Extension Reference Out-of-Bounds Read","id":"CVE-2026-40026"},"packages":[],"prev":{"headline":"Sleuth Kit tsk_recover Path Traversal","id":"CVE-2026-40024"},"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.4,"headline":"Sleuth Kit tsk_recover Path Traversal","id":"CVE-2026-40024","kev_date_added":null,"published":"2026-04-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":"An attacker can craft a malicious APFS disk image to trigger an out-of-bounds read in Sleuth Kit, leading to information disclosure or application crashes.","url":"https://insights.sbomify.com/CVE-2026-40025/"}