Quick answers
- Is CVE-2026-106579 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-106579 being exploited in the wild.
- How severe is CVE-2026-106579?
- Medium severity, with a CVSS score of 6.2, 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-106579?
- 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-106579 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-106579?
- 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 is a policy validation bypass in the coder authorization check during image read and write operations. The flaw exists in MagickCore/constitute.c where the wrong variable is passed to the IsCoderAuthorized function, causing the policy check to evaluate against an incorrect coder identifier. An attacker can supply a crafted image that bypasses coder-based security policies without requiring authentication or special privileges.
Affected products
- ImageMagick ImageMagick Prior to 7.1.2-31 and 6.9.13-56
Timeline
- 2026-10-07: disclosed