# CVE-2026-109964: ImageMagick before 7.1.2-33 and 6.9.13-58 Heap Buffer Underwrite in PICT Decoder

> Attackers can achieve code execution or cause denial of service by supplying a crafted PICT file to vulnerable ImageMagick versions.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/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:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-109964, ECHO-88a2-2fcc-be2a, GHSA-279f-3w5r-54f5, GHSA-mqmp-r5jh-jx7w, UBUNTU-CVE-2026-109964

## What is CVE-2026-109964?

CVE-2026-109964 is a medium-severity memory corruption vulnerability in ImageMagick, published on 13 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ImageMagick before 7.1.2-33 and 6.9.13-58 contains a heap buffer underwrite vulnerability in DecodeImage() in coders/pict.c on 32-bit builds due to pointer arithmetic overflow. Attackers can supply a crafted PICT file with maximized row, column and bytes-per-line values to bypass bounds checks and write up to 128 controlled bytes below the heap buffer, causing crashes or code execution.

Weakness: CWE-124 (Buffer Underwrite)

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


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

Upgrade to a fixed version.

## Is CVE-2026-109964 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109964 is a medium-severity memory corruption vulnerability in ImageMagick, published on 13 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-109964 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-109964/ (Markdown: https://insights.sbomify.com/CVE-2026-109964/index.md)
```

## Sources

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

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