# CVE-2026-109258: ImageMagick 7.1.0-20 before 7.1.2-32 Invalid Memory Free in FX Operation

> Attackers can trigger an invalid memory free in ImageMagick's FX operation, causing crashes or potential code execution via crafted images.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:L/AT:P/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-109258, ECHO-29b5-7010-50b8, GHSA-pv8x-gq6w-gp4r, GHSA-qr3h-jrh3-5m34, UBUNTU-CVE-2026-109258

## What is CVE-2026-109258?

CVE-2026-109258 is a low-severity use after free 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 7.1.0-20 before 7.1.2-32 contains an invalid memory free vulnerability in the fx operation that occurs when initialization of an FX runtime entry fails. Attackers can trigger the failed FX runtime initialization to cause an invalid free, resulting in memory corruption and application crashes.

Weakness: CWE-476 (NULL Pointer Dereference)

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


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

Upgrade to a fixed version.

## Is CVE-2026-109258 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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