ImageMagick CVE-2026-116145

Exploitation requires a deployment that actually configures ImageMagick security-policy restrictions (policy.xml) to block specific coders or operations - the bug only matters where that policy is relied on as a boundary; against a default install with no restrictive policy there is nothing to bypass. The attacker must also be able to supply input that ImageMagick processes. Limiting factors per the vendor CVSS 4.0 vector: local vector (AV:L), high attack complexity (AC:H), a present attack requirement (AT:P), and high privileges required (PR:H), with no user interaction; impact is limited to Low across confidentiality, integrity, and availability. The specific trigger of the residual bypass is not described in the available sources.

All signals point to a low real-world priority. The vendor CVSS 4.0 base score is 1.8 (Low) with vector AV:L/AC:H/AT:P/PR:H/UI:N and only Low confidentiality/integrity/availability impact to the vulnerable system (VC:L/VI:L/VA:L, no subsequent-system impact). The flaw is a CWE-693 protection-mechanism (security-policy) bypass - a defense-in-depth weakening rather than a direct code-execution or data-disclosure bug, which is why impact metrics are all Low. The vuln.today decision label is 'monitor', consistent with the low score. No EPSS score and no CISA KEV entry were provided in the input, and no exploitation-probability signal is available to contrast against. The references are vendor/analyst advisories (GHSA, VulnCheck), not exploit code, so there is no public exploit identified at time of analysis. The notable nuance is that this is explicitly an INCOMPLETE FIX of a prior bypass (GHSA-jjp4-3fwf-393j), meaning the original hardening remains partially defeatable; organizations that depend on ImageMagick's policy.xml as a security boundary should still apply the update, but there is no evidence of urgency. Net: a genuine low-severity, defense-in-depth issue, not a high-CVSS-but-low-risk mismatch - the score and the decision label agree.

An actor who can submit crafted input to an ImageMagick instance whose operator relies on a configured policy.xml to block certain coders or operations supplies input that evades those restrictions, causing ImageMagick to perform an operation the policy was meant to deny. Because this is an incomplete fix of a prior bypass, the residual gap is exercised the same way. No public working exploit code was identified in the provided sources, and the exact trigger is not described in the available evidence.