Process crash via SIXEL reallocation integer overflow
Published Feb 24, 2026 · Updated Feb 24, 2026
Signed integer overflow in ImageMagick before 6.9.13-40 and 7.0.0 through 7.1.2-14 allows remote attackers to crash processes. The SIXEL decoder uses signed 32-bit pointer arithmetic while reallocating its image buffer, allowing crafted dimensions to overflow and corrupt memory. No privileges or user interaction are required when an exposed workflow processes a malicious SIXEL image; the reported consequence is a process crash.
Summary
What happened
Signed integer overflow in ImageMagick before 6.9.13-40 and 7.0.0 through 7.1.2-14 allows remote attackers to crash processes. The SIXEL decoder uses signed 32-bit pointer arithmetic while reallocating its image buffer, allowing crafted dimensions to overflow and corrupt memory. No privileges or user interaction are required when an exposed workflow processes a malicious SIXEL image; the reported consequence is a process crash.
The record
- CVE
- CVE-2026-25970
- Published
- Feb 24, 2026
- Updated
- Feb 24, 2026
- Vendor
- ImageMagick Studio LLC
- Product
- ImageMagick
- Classifications
- CWE-190, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 24, 2026CVE publishedPublication date reported by the CVE source.
- Feb 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 6.9.13-40
- Affected versionversion=>= 7.0.0, < 7.1.2-15
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo