# CVE-2026-109276: ImageMagick before 6.9.13-57 and 7.x before 7.1.2-32 Temporary File Leak in JNG Decoder

> Attackers can cause disk space exhaustion and service degradation by submitting crafted JNG files that leak temporary files in ImageMagick.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Oct 2026
- **Updated:** 18 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-109276, ECHO-757a-55db-aa30, GHSA-f983-243h-9x4r, GHSA-hh36-f88v-939q, UBUNTU-CVE-2026-109276

## What is CVE-2026-109276?

CVE-2026-109276 is a medium-severity denial of service vulnerability in ImageMagick, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ImageMagick before 6.9.13-57 and 7.x before 7.1.2-32 contains an incomplete cleanup flaw in the JNG decoder that fails to remove temporary files when processing crafted input. Attackers can submit crafted JNG files for processing to repeatedly leak temporary files, consuming disk space and degrading availability.

Weakness: CWE-459 (Incomplete Cleanup)

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


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

Upgrade to a fixed version.

## Is CVE-2026-109276 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109276 is a medium-severity denial of service vulnerability in ImageMagick, published on 12 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109276 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-109276/ (Markdown: https://insights.sbomify.com/CVE-2026-109276/index.md)
```

## Sources

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

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