Quick answers
- Is CVE-2026-106578 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106578 being exploited in the wild.
- How severe is CVE-2026-106578?
- Medium severity, with a CVSS score of 5.9, published 7 October 2026.
- Which products and versions are affected?
- ImageMagick prior to 7.1.2-31 and 6.9.13-56.
- Is there a fix for CVE-2026-106578?
- Yes: fixed in 7.1.2-31, 6.9.13-56. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-106578 attacked?
- It is attacked over the network or with local access.
- Am I affected by CVE-2026-106578?
- 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: 7.1.2-31, 6.9.13-56
Technical details
The vulnerability exists in the MVG decoder's RenderMVGContent function, where the CheckPrimitiveExtent call was made with an incorrect parameter, causing use of uninitialized heap memory and subsequent invalid free. The flaw is triggered when processing a crafted image via the MVG format, requiring no authentication or user privileges beyond the ability to supply an image file. An attacker can crash the process or potentially achieve code execution through heap corruption.
Affected products
- ImageMagick ImageMagick prior to 7.1.2-31 and 6.9.13-56
Timeline
- 2026-10-07: disclosed