All reports
Medium

ImageMagick's Security Policy Bypass through config/policy-secure.xml via "fd handler" leads to stdin/stdout access

Affected versions

Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
< 14.10.3
Fixed version
14.10.3
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-25966

Probability of exploitation in the next 30 days: 0.15%

FIRST EPSS · 2026-11-20

Description

The shipped “secure” security policy includes a rule intended to prevent reading/writing from standard streams:

<policy domain="path" rights="none" pattern="-"/>

However, ImageMagick also supports fd: pseudo-filenames (e.g., fd:0, fd:1). This path form is not blocked by the secure policy templates, and therefore bypasses the protection goal of “no stdin/stdout”.

To resolve this, users can add the following change to their security policy.

<policy domain="path" rights="none" pattern="fd:*"/>

And this will also be included in ImageMagick's more secure policies by default.

Links