Service interruption via unsafe magnify defaults
Published Jul 11, 2026 · Updated Jul 11, 2026
Heap buffer overflow in ImageMagick before 7.1.2-19 allows local users to interrupt image processing via an unrecognized magnify method. MagnifyImage in MagickCore/resize.c leaves magnification and width at undersized defaults for an unrecognized magnify:method, causing a four-byte read past a heap allocation. Triggering requires an operator or application to process attacker-controlled magnify input, and the published assessment limits the consequence to availability.
Summary
What happened
Heap buffer overflow in ImageMagick before 7.1.2-19 allows local users to interrupt image processing via an unrecognized magnify method. MagnifyImage in MagickCore/resize.c leaves magnification and width at undersized defaults for an unrecognized magnify:method, causing a four-byte read past a heap allocation. Triggering requires an operator or application to process attacker-controlled magnify input, and the published assessment limits the consequence to availability.
The record
- CVE
- CVE-2026-56372
- Published
- Jul 11, 2026
- Updated
- Jul 11, 2026
- Vendor
- ImageMagick Studio LLC
- Product
- ImageMagick
- Classifications
- CWE-122
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 11, 2026CVE publishedPublication date reported by the CVE source.
- Jul 11, 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 <7.1.2-19
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