ImageMagick has a heap buffer over-write on 32-bit systems in SFW decoder

Vulnerability

Overview

CVE-2026-31853 describes an integer overflow vulnerability in the SFW (Sun Rasterfile) decoder of ImageMagick, a widely used open-source image processing suite. The flaw occurs specifically on 32-bit systems when the decoder attempts to handle extremely large images, leading to a heap buffer over-write can be triggered, leading to a crash. The root cause is an arithmetic overflow during size calculations, which is not properly checked before memory allocation or data copying [1][2][4].

Exploitation and

Attack Surface

An attacker can exploit this vulnerability by providing a specially crafted, oversized SFW image file to an application or service that uses ImageMagick to process images. No authentication is required, authentication is required, and the attack can be delivered remotely if the application accepts user-uploaded images. The vulnerability is triggered during decoding, meaning any service that automatically processes images (e.g., web upload handlers, thumbnail generators) could be at risk. The attack complexity is considered low, as it only requires crafting a malformed image file [2][4].

Impact

Successful exploitation results in a heap buffer over-write, which can cause a denial of service disruption (denial of service) due to application crash. In some cases, this type of memory corruption could potentially be leveraged for arbitrary code execution, though the primary impact described is a crash. The vulnerability affects the availability of the system's availability, and depending on the context, could also lead to information disclosure or integrity compromise [2][4].

Mitigation

The vulnerability has been patched in ImageMagick versions 7.1.2-16 and 6.9.13-41, released on March 8, 2026. Users are strongly advised to update to these versions or later. For those using the .NET wrapper Magick.NET, version 14.10.4 includes the fix. No workarounds are mentioned, but limiting image upload sizes and using security policies to restrict SFW files can reduce risk [1][3][4].