# CVE-2026-109279: ImageMagick before 6.9.13-57 and 7.x before 7.1.2-32 Heap Buffer Overflow via Concurrent Security Policy Access

> Concurrent access to security policies in ImageMagick causes a heap buffer overflow, allowing attackers to crash the application via denial of service.

- **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-109279, ECHO-d75c-fc61-5045, GHSA-8x3v-wr32-qqh4, GHSA-xg3c-hhwj-7xrg, UBUNTU-CVE-2026-109279

## What is CVE-2026-109279?

CVE-2026-109279 is a low-severity 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 6.9.13-57 and 7.x before 7.1.2-32 lacks proper synchronization when the security policy is accessed, so simultaneous reads and writes of the policy by multiple threads trigger a race condition that causes a heap buffer over-write. An attacker able to induce concurrent security policy access can crash the application, causing a denial of service.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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


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

Upgrade to a fixed version.

## Is CVE-2026-109279 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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