# CVE-2026-120454: The Sleuth Kit through 4.15.0 NULL Pointer Dereference via decmpfs LZVN Decompression


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** AZL-112817, DEBIAN-CVE-2026-120454, GHSA-gr3p-v4fr-f93c, UBUNTU-CVE-2026-120454

## What is CVE-2026-120454?

CVE-2026-120454 is a medium-severity vulnerability in The Sleuth Kit, published on 2 Nov 2026. 

### Official description

The Sleuth Kit through 4.15.0 contains a NULL pointer dereference vulnerability in decmpfs_decompress_lzvn_attr() that allows attackers to crash the tool by supplying a crafted HFS+ image. Attackers can set a huge uncompressed_size in an LZVN inline com.apple.decmpfs attribute so allocation fails and the decoder writes through NULL, causing denial of service.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2026-120454?


## How do I fix CVE-2026-120454?

No fix has been published for CVE-2026-120454 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-120454 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120454 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120454 and fix it if it is affected.

What it is: CVE-2026-120454 is a medium-severity vulnerability in The Sleuth Kit, published on 2 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120454 exists.

Affected product: The Sleuth Kit. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120454/ (Markdown: https://insights.sbomify.com/CVE-2026-120454/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120454
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120454
- OSV: https://osv.dev/vulnerability/CVE-2026-120454

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120454/
Summaries are generated and may contain mistakes; the official description above is the record.
