CVE-2026-25966: ImageMagick's Security Policy Bypass through config/policy-secure.xml via "fd handler" leads to stdin/stdout access
ImageMagick is free and open-source software used for editing and manipulating digital images. The shipped "secure" security policy includes a rule intended to prevent reading/writing from standard streams. However, ImageMagick also supports fd:<n> pseudo-filenames (e.g., fd:0, fd:1). Prior to versions 7.1.2-15 and 6.9.13-40, this path form is not blocked by the secure policy templates, and therefore bypasses the protection goal of "no stdin/stdout." Versions 7.1.2-15 and 6.9.13-40 contain a patch by including a change to the more secure policies by default. As a workaround, add the change to one's security policy manually.
Security readout for executives and security teams
Plain-English summary
ImageMagick’s bundled secure policy was meant to block access to standard input and output, but older versions missed an alternate file descriptor naming path. Organizations using that policy as a security boundary could have limited confidentiality, integrity, or availability exposure if ImageMagick handles attacker-controlled inputs or workflows.
Executive priority
Treat as a moderate-priority hardening issue. Patch during the next security maintenance window, sooner for internet-facing or multi-tenant image processing services that rely on ImageMagick’s secure policy controls.
Technical view
Before ImageMagick 7.1.2-15 and 6.9.13-40, secure policy templates did not block fd:<n> pseudo-filenames, bypassing the intended no-stdin/stdout restriction. The CVE is rated CVSS 5.9 with local attack vector and low confidentiality, integrity, and availability impact.
Likely exposure
Exposure is most likely where ImageMagick is installed before the fixed versions and configured with the shipped secure policy to restrict standard stream access. Risk is higher in conversion services, automation, or upload pipelines that process untrusted image-related input.
Exploitation context
The provided sources do not report active exploitation, and KEV status is false. The issue is a policy bypass, not evidence of broad remote compromise. Real risk depends on whether local or application-mediated ImageMagick usage allows attacker influence over input paths or processing behavior.
Researcher notes
Evidence supports a CWE-284 security policy bypass involving fd pseudo-filenames. The source bundle names affected version ranges, fixed versions, CVSS vector, and workaround direction, but does not provide exploitation telemetry or broader product impact beyond ImageMagick.
Mitigation direction
Upgrade ImageMagick to 7.1.2-15, 6.9.13-40, or later.
Apply the vendor-described manual security policy change if immediate upgrade is unavailable.
Review ImageMagick security advisory GHSA-xwc6-v6g8-pw2h for exact vendor guidance.
Prioritize systems processing untrusted uploads, batch jobs, or user-supplied image operations.
Validation and detection
Inventory deployed ImageMagick versions across servers, containers, and build images.
Confirm versions are at least 7.1.2-15 or 6.9.13-40.
Review security policy files for the vendor change blocking file descriptor stream access.
Identify workflows that rely on the secure policy to prevent stdin/stdout access.
Check whether applications pass user-controlled inputs into ImageMagick operations.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-284 · source CWE mapping
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.