# CVE-2026-116151: ImageMagick before 6.9.13-58 and 7.x before 7.1.2-33 Memory Leak in JNG Encoder


- **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-116151, ECHO-f64a-5a96-dd9b, GHSA-gghq-4x95-r2h2, GHSA-v9q4-cm37-q2jm, UBUNTU-CVE-2026-116151

## What is CVE-2026-116151?

CVE-2026-116151 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 memory leak in the JNG encoder that fails to release allocated memory when processing a crafted image. Attackers can supply crafted images that are encoded to JNG to leak memory, potentially causing resource exhaustion and a limited denial of service.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

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


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

Upgrade to a fixed version.

## Is CVE-2026-116151 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116151 is a medium-severity vulnerability in ImageMagick, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116151 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-116151/ (Markdown: https://insights.sbomify.com/CVE-2026-116151/index.md)
```

## Sources

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

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