# CVE-2026-116140: ImageMagick before 6.9.13-58 and 7.x before 7.1.2-33 Policy Bypass via Delegate Invocation Parsing


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 25 Oct 2026
- **Updated:** 25 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-116140, ECHO-1bab-a60d-a052, GHSA-528x-2384-jmxp, GHSA-cp2f-7vrw-mcqf, UBUNTU-CVE-2026-116140

## What is CVE-2026-116140?

CVE-2026-116140 is a medium-severity vulnerability in ImageMagick, published on 25 Oct 2026. 

### Official description

ImageMagick before 6.9.13-58 and 7.x before 7.1.2-33 incorrectly parses delegate invocations, which can allow an executable blocked in policy.xml to still run. An attacker who gets ImageMagick to process input that triggers a delegate invocation can bypass the administrator-defined policy and execute the blocked program.

Weakness: CWE-863 (Incorrect Authorization)

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


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

Upgrade to a fixed version.

## Is CVE-2026-116140 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116140 is a medium-severity vulnerability in ImageMagick, published on 25 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116140 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-116140/ (Markdown: https://insights.sbomify.com/CVE-2026-116140/index.md)
```

## Sources

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

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