Quick answers
- Is CVE-2026-109275 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109275 being exploited in the wild.
- How severe is CVE-2026-109275?
- Medium severity, with a CVSS score of 4.8, published 12 October 2026.
- Which products and versions are affected?
- ImageMagick 6.9.13-56 and earlier; 7.0.0 through 7.1.2-31.
- Is there a fix for CVE-2026-109275?
- Yes: fixed in ImageMagick 6.9.13-57, 7.1.2-32. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-109275 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-109275?
- Check whether you run ImageMagick at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: ImageMagick 6.9.13-57, 7.1.2-32
Technical details
The MVG decoder in ImageMagick fails to properly validate or sanitize PostScript font names before passing them to the PostScript renderer, allowing code injection via a crafted MVG file. The vulnerability requires network-based delivery of the malicious MVG file and the PostScript renderer to be active. An attacker gains the ability to inject arbitrary PostScript commands, potentially leading to code execution or availability impact.
Affected products
- ImageMagick 6.9.13-56 and earlier; 7.0.0 through 7.1.2-31
Timeline
- 2026-09-27: disclosed: GitHub Security Advisory GHSA-233r-2p53-wqf5 published
- 2026-09-27: patched: Fix released in ImageMagick 6.9.13-57 and 7.1.2-32
- 2026-10-12: advisory: Published on NVD