# CVE-2026-116147: ImageMagick before 6.9.13-58 and 7.x before 7.1.2-33 Null Pointer Dereference in DJVU Decoder


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 25 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-116147, ECHO-bb49-8013-7d08, GHSA-fg5p-f6qx-gv7g, GHSA-v5f5-4v9x-p3f2, UBUNTU-CVE-2026-116147

## What is CVE-2026-116147?

CVE-2026-116147 is a medium-severity vulnerability in ImageMagick, published on 25 Oct 2026. 

### Official description

ImageMagick before 6.9.13-58 and 7.x before 7.1.2-33 contains a null pointer dereference in the DJVU decoder because the result of a memory allocation is not checked before use. Attackers can supply a DJVU image that, when processed under conditions where the allocation fails, crashes the process and causes a denial of service.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

Upgrade to a fixed version.

## Is CVE-2026-116147 being exploited?

There is no known exploitation of CVE-2026-116147 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116147 is a medium-severity vulnerability in ImageMagick, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116147 in the wild and no public exploit code.

Affected product: ImageMagick. 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-116147/ (Markdown: https://insights.sbomify.com/CVE-2026-116147/index.md)
```

## Sources

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

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