# CVE-2026-116148: ImageMagick before 6.9.13-58 and 7.x before 7.1.2-33 Code Injection via MVG Encoder Drawing Options


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:L/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-116148, ECHO-7ad7-ff1e-d057, GHSA-g4fj-jwfv-j2rp, GHSA-qq8x-fq3x-43h4, UBUNTU-CVE-2026-116148

## What is CVE-2026-116148?

CVE-2026-116148 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 contains an injection vulnerability in the MVG encoder, which does not properly neutralize user-specified drawing options before writing them into generated MVG output. Attackers who can supply drawing options can inject arbitrary MVG drawing commands into the resulting MVG file.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

Upgrade to a fixed version.

## Is CVE-2026-116148 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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