Quick answers
- Is CVE-2026-40026 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-40026 being exploited in the wild.
- How severe is CVE-2026-40026?
- Medium severity, with a CVSS score of 4.4, published 8 April 2026.
- Which products and versions are affected?
- Sleuth Kit The Sleuth Kit through 4.14.0.
- Is there a fix for CVE-2026-40026?
- A patch was published on 2026-03-01: Fix merged into develop-4.14 branch Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-40026 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-40026?
- Check whether you run Sleuthkit The Sleuth Kit. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An out-of-bounds read vulnerability exists in the ISO9660 filesystem parser within the `parse_susp()` function. The root cause is the improper validation of `len_id`, `len_des`, and `len_src` fields from the disk image, which are trusted during `memcpy` operations into a stack buffer without verifying they remain within the bounds of the SUSP block. Additionally, a zero-length SUSP entry can trigger an infinite parsing loop, leading to a denial of service. Exploitation requires a user to open a maliciously crafted ISO image. A fix has been committed to the project's repository (commit a95b0ac).
Affected products
- Sleuth Kit The Sleuth Kit through 4.14.0
Timeline
- 2026-03-01: patched: Fix merged into develop-4.14 branch
- 2026-04-08: disclosed: Initial disclosure by VulnCheck and Mobasi
- 2026-04-08: advisory: NVD publication date