CVE-2026-86424 — ImageMagick before 7.1.2-30 Path Traversal via TOCTOU Symlink Race

ImageMagick before 7.1.2-30 and 6.9.13-55 contains a time-of-check-time-of-use (TOCTOU) vulnerability in the video decoder that allows attackers to bypass path policy write restrictions via symlink swaps. An attacker can replace a symlink between policy validation (check-time) and the file write operation (use-time) to write to policy-denied locations.

Published Sep 7, 2026Updated Sep 7, 2026Sources: cvelistV5, VulnCheck

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

chance of exploitation in 30 days

Affects

imagemagick

CVSS base

2.5

LOW

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

imagemagick

Products (1)

imagemagick

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
2.5	CVSS 3.1	LOW	—	—	cvelistV5

Weakness & attack patterns

CWE-59

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

T1547.009Boot or Logon Autostart Execution: Shortcut Modification
T1574.005Hijack Execution Flow: Executable Installer File Permissions Weakness
T1574.010Hijack Execution Flow: Services File Permissions Weakness

References

2 on the record

github.com/ImageMagick/ImageMagick/security/advisories/GHSA-9x6f-98x9-rx6g
vendor-advisory
www.vulncheck.com/advisories/imagemagick-before-7.1.2-30-path-traversal-via-toctou-symlink-race
third-party-advisory

Elsewhere on this site

imagemagickevery CVE for this vendor
CWE-59other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.