# CVE-2026-109264: ImageMagick before 6.9.13-57 and 7.x before 7.1.2-32 Stack Overflow in MVG Decoder

> An attacker can cause a denial of service by triggering a stack overflow in the MVG decoder via a crafted file name.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/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:** 13 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-109264, ECHO-e6d4-4fce-ef3f, GHSA-3xv5-cm4v-6wpv, GHSA-pmqj-84pr-qc7c, UBUNTU-CVE-2026-109264

## What is CVE-2026-109264?

CVE-2026-109264 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 uncontrolled recursion in the MVG decoder that can exhaust the program stack. An attacker who controls a file name processed by ImageMagick can trigger a stack overflow that crashes the process, causing a denial of service.

Weakness: CWE-674 (Uncontrolled Recursion)

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


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

Upgrade to a fixed version.

## Is CVE-2026-109264 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109264 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-109264 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-109264/ (Markdown: https://insights.sbomify.com/CVE-2026-109264/index.md)
```

## Sources

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

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