# CVE-2026-130660: ImageMagick before 7.1.2-35 Heap Buffer Over-Read in MVG Decoder


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-h87p-hxcv-f65r, GHSA-m9p2-wqc3-mj22

## What is CVE-2026-130660?

CVE-2026-130660 is a medium-severity vulnerability in ImageMagick, published on 18 Nov 2026. 

### Official description

ImageMagick before 7.1.2-35 contains a heap buffer over-read vulnerability in the MVG decoder that allows attackers to read out-of-bounds memory by supplying a crafted file. Attackers can provide a malicious MVG file for processing to trigger the over-read, causing application crashes or exposure of heap memory contents.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

No fix has been published for CVE-2026-130660 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-130660 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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