CVE-2026-116140 in ImageMagick
Summary
by MITRE • 10/25/2026
ImageMagick before 6.9.13-58 and 7.x before 7.1.2-33 incorrectly parses delegate invocations, which can allow an executable blocked in policy.xml to still run. An attacker who gets ImageMagick to process input that triggers a delegate invocation can bypass the administrator-defined policy and execute the blocked program.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 10/25/2026
The vulnerability identified involves a critical flaw in how ImageMagicon processes delegate invocations, specifically affecting versions prior to 6.9.13-58 and version 7.x prior to 7.1.2-33. This issue stems from an incorrect parsing mechanism that fails to properly enforce security policies defined within the policy.xml configuration file. In a standard ImageMagick deployment, administrators utilize this XML-based policy file to restrict or block specific external programs known as delegates. These delegates are helper applications invoked by ImageMagick to handle certain image formats or operations that the core library does not support natively. The intended security model relies on strict adherence to these policies to prevent unauthorized execution of system commands, thereby mitigating risks associated with processing untrusted input data.
The technical flaw lies in the parsing logic used when evaluating delegate invocations against the policy rules. Due to this implementation error, ImageMagick may fail to recognize or apply restrictions that should block certain executable programs. Consequently, even if a specific command is explicitly listed as blocked within the policy.xml file, the application proceeds with its execution during image processing operations. This bypass of administrative controls represents a significant deviation from expected security behavior, effectively nullifying one of the primary defense mechanisms available to system administrators for controlling external program execution through ImageMagick.
From an operational perspective, this vulnerability allows attackers who can induce ImageMagick to process maliciously crafted input files to execute arbitrary commands on the host system. By crafting images that trigger specific delegate invocations corresponding to blocked executables, an attacker can achieve remote code execution without needing elevated privileges or direct access to the file system beyond what is required for image processing services. This capability transforms a simple image conversion tool into a potential vector for full system compromise, particularly in environments where ImageMagick processes user-uploaded content such as web applications, document management systems, or automated media pipelines that do not sufficiently sanitize input before passing it to the library.
This vulnerability aligns with Common Weakness Enumeration CWE-94, which describes Improper Control of Generation of Code (Code Injection), and more specifically relates to CWE-78, Improper Neutralization of Special Elements used in an OS Command (OS Command Injection). The failure to enforce policy restrictions constitutes a breakdown in access control mechanisms that are designed to limit the scope of actions permitted by software components. In terms of adversary tactics, this flaw facilitates techniques associated with MITRE ATT&CK T1059, specifically command and script interpretation, allowing attackers to execute system commands as part of their exploitation chain. The ability to bypass policy blocks significantly lowers the barrier for initial access and lateral movement in compromised environments where ImageMagick is deployed.
Mitigation strategies primarily involve upgrading to patched versions that correct the parsing logic for delegate invocations. Administrators should ensure they are running ImageMagick version 6.9.13-58 or later, or version 7.1.2-33 and newer, where these policy enforcement mechanisms have been rectified. Additionally, organizations should review their existing security configurations to verify that the policy.xml file is correctly structured and that all necessary delegates are appropriately restricted. Implementing additional layers of defense such as containerization with strict capabilities restrictions or using dedicated image processing services isolated from critical system resources can further reduce the impact if a vulnerability were to be exploited in legacy systems before patching is feasible. Regular auditing of delegate usage and keeping software dependencies updated remains essential for maintaining robust security postures against similar implementation flaws.