CVE-2026-25897
Integer Overflow in ImageMagick Sun Decoder Causes Heap Corruption
Publication date: 2026-02-24
Last updated on: 2026-02-24
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| imagemagick | imagemagick | to 6.9.13-40 (exc) |
| imagemagick | imagemagick | From 7.0.0-0 (inc) to 7.1.2-15 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-122 | A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). |
| CWE-190 | The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-25897 is a moderate severity vulnerability in 32-bit builds of ImageMagick versions prior to 7.1.2-15 and 6.9.13-40. It involves an integer overflow in the sun decoder component, which can cause a heap buffer overflow leading to an out-of-bounds write when processing a specially crafted image file.
How can this vulnerability impact me? :
This vulnerability can be exploited remotely without requiring privileges or user interaction. It allows an attacker to corrupt heap memory, causing a denial of service by impacting the availability of the affected system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability was identified through AddressSanitizer, which detected a heap-buffer-overflow error during a write operation. Therefore, using AddressSanitizer or similar memory error detection tools when processing images with ImageMagick can help detect this issue.
Since the vulnerability is triggered by processing specially crafted image files, monitoring or analyzing ImageMagick logs for crashes or abnormal behavior when handling image files may indicate exploitation attempts.
No specific commands are provided in the resources, but running ImageMagick commands on suspicious or untrusted images under AddressSanitizer instrumentation could help detect the vulnerability.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to upgrade ImageMagick to versions 7.1.2-15 or 6.9.13-40 or later, as these versions contain the patch that fixes the integer overflow vulnerability in the sun decoder.
Additionally, avoid processing untrusted or specially crafted image files on vulnerable 32-bit builds of ImageMagick to reduce the risk of exploitation.