Stack corruption via unchecked morphology kernel copy
Published Mar 9, 2026 · Updated Mar 9, 2026
Stack buffer overflow in ImageMagick before 7.1.2-16 and 6.9.13-41 allows local users to corrupt process memory via a crafted kernel string. The morphology kernel parsers pass user-controlled kernel names or arrays to memcpy, copying them into fixed-size stack buffers without checking their lengths. Exploitation requires local delivery and user interaction with a morphology operation; the resulting corruption can alter memory or terminate the process.
Summary
What happened
Stack buffer overflow in ImageMagick before 7.1.2-16 and 6.9.13-41 allows local users to corrupt process memory via a crafted kernel string. The morphology kernel parsers pass user-controlled kernel names or arrays to memcpy, copying them into fixed-size stack buffers without checking their lengths. Exploitation requires local delivery and user interaction with a morphology operation; the resulting corruption can alter memory or terminate the process.
The record
- CVE
- CVE-2026-28494
- Published
- Mar 9, 2026
- Updated
- Mar 9, 2026
- Vendor
- ImageMagick Studio LLC
- Product
- ImageMagick
- Classifications
- CWE-121
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 9, 2026CVE publishedPublication date reported by the CVE source.
- Mar 9, 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