Out-of-bounds read via off-by-one morphology validation
Published Jun 30, 2026 · Updated Jun 30, 2026
Out-of-bounds read in ImageMagick before 6.9.13-44 or 7.1.2-19 allows local users to interrupt processing via invalid morphology parameters. Morphology origin validation accepts a coordinate one pixel beyond the valid image boundary, after which processing reads a four-byte pixel outside the heap allocation. Exploitation requires another user to invoke the malformed morphology operation; the documented effect is a single-pixel read and processing interruption, not a write primitive.
Summary
What happened
Out-of-bounds read in ImageMagick before 6.9.13-44 or 7.1.2-19 allows local users to interrupt processing via invalid morphology parameters. Morphology origin validation accepts a coordinate one pixel beyond the valid image boundary, after which processing reads a four-byte pixel outside the heap allocation. Exploitation requires another user to invoke the malformed morphology operation; the documented effect is a single-pixel read and processing interruption, not a write primitive.
The record
- CVE
- CVE-2026-56361
- Published
- Jun 30, 2026
- Updated
- Jun 30, 2026
- Vendor
- ImageMagick Studio LLC
- Product
- ImageMagick
- Classifications
- CWE-193, CWE-125, T1499
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 30, 2026CVE publishedPublication date reported by the CVE source.
- Jun 30, 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=0 <6.9.13-44
- Affected versionversion=0 <7.1.2-19
What conditions does exploitation require?
What is affected?
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