# CVE-2026-109271: ImageMagick 7.1.2-30 before 7.1.2-32 Use After Free in WBINFO Decoder

> Attackers can cause a denial of service by supplying a crafted image that triggers a use-after-free error in the WBINFO decoder during memory allocation failures.

- **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:** 18 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-109271, ECHO-5397-77d3-70b8, GHSA-h82h-8q6v-f57g, GHSA-vxwm-jfjc-3r4x, UBUNTU-CVE-2026-109271

## What is CVE-2026-109271?

CVE-2026-109271 is a medium-severity use after free 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 7.1.2-30 before 7.1.2-32 contains a use after free vulnerability in the WBINFO decoder that occurs when a memory allocation fails during image decoding. Attackers can supply a crafted image that, when decoded under memory allocation failure conditions, causes freed memory to be reused, crashing the application.

Weakness: CWE-415 (Double Free)

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


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

Upgrade to a fixed version.

## Is CVE-2026-109271 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109271 is a medium-severity use after free 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-109271 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-109271/ (Markdown: https://insights.sbomify.com/CVE-2026-109271/index.md)
```

## Sources

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

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