Local memory corruption via failed SIXEL reduction
Published Mar 12, 2026 · Updated Mar 12, 2026
Stack buffer overflow in ImageMagick 7 before 7.1.2-16 and ImageMagick 6 before 6.9.13-41 allows local users to corrupt memory. When allocation failure prevents color reduction, WriteSIXELImage continues with image->colors above SIXEL_PALETTE_MAX and writes beyond its stack palette buffer. Successful exploitation requires local access and an allocation failure; the overwrite corrupts process memory, with no reported data disclosure.
Summary
What happened
Stack buffer overflow in ImageMagick 7 before 7.1.2-16 and ImageMagick 6 before 6.9.13-41 allows local users to corrupt memory. When allocation failure prevents color reduction, WriteSIXELImage continues with image->colors above SIXEL_PALETTE_MAX and writes beyond its stack palette buffer. Successful exploitation requires local access and an allocation failure; the overwrite corrupts process memory, with no reported data disclosure.
The record
- CVE
- CVE-2026-32259
- Published
- Mar 12, 2026
- Updated
- Mar 12, 2026
- Vendor
- ImageMagick Studio LLC
- Product
- ImageMagick
- Classifications
- CWE-121
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2026CVE publishedPublication date reported by the CVE source.
- Mar 12, 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-41
- Affected versionversion=>= 7.0.0, < 7.1.2-16
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