# CVE-2026-109270: ImageMagick before 7.1.2-32 Memory Leak via -process Option

> Attackers can exhaust memory and degrade service availability by repeatedly invoking the -process option with crafted arguments in ImageMagick.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-109270, ECHO-ac43-555f-0f60, GHSA-f32c-2v6j-wvh5, GHSA-qrq6-phpr-492q, UBUNTU-CVE-2026-109270

## What is CVE-2026-109270?

CVE-2026-109270 is a medium-severity denial of service vulnerability in ImageMagick, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ImageMagick before 7.1.2-32 contains a memory leak vulnerability in the -process option that allows attackers to cause unreleased memory allocations by supplying certain arguments. Attackers can repeatedly invoke the -process option with crafted arguments to gradually exhaust memory and degrade service availability.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-109270 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109270 is a medium-severity denial of service vulnerability in ImageMagick, published on 12 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-109270 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-109270/ (Markdown: https://insights.sbomify.com/CVE-2026-109270/index.md)
```

## Sources

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

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