CVE-2026-105081: ImageMagick · Link Following
Affects ImageMagickSource CVE Database V5
Not known to be exploited · CVSS 2.0 Low : upgrade to 7.1.2-33 when convenient.
Data as of 29 Oct 2026, 21:45 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 2.0 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 3.6 |
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-13.
- Patch
- Available – fixed in 7.1.2-33, 6.9.13-58
CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 12 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade ImageMagick to 7.1.2-33; ImageMagick to 6.9.13-58.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ImageMagickImageMagick | Affected
| Fixed in
|
| ImageMagickImageMagick | Affected
| Fixed in
|
AI-suggested
A fix is available in ImageMagick versions 6.9.13-58 and 7.1.2-33. Users should upgrade to these or later versions to remediate this vulnerability. No additional mitigation steps are indicated beyond applying the official patches.
Description
ImageMagick before 6.9.13-58 and 7.x before 7.1.2-33 does not properly account for symbolic links in the IsRightsAuthorizedByName security policy check, allowing configured policy restrictions to be bypassed. Local attackers who can create a symlink can point it at a policy-restricted path to evade the configured policy.