Local memory over-allocation via unchecked scene count
Published Sep 18, 2026 · Updated Sep 18, 2026
Resource-limit bypass in ImageMagick before 7.1.2-31 and before 6.9.13-56 allows local users to over-allocate memory through scene selection. The PCD, CUBE, and HALD readers clone and append an image for each nonzero scene count without first acquiring the configured list-length resource. Exploitation requires control of command-line options and can exceed the intended memory policy, producing a limited availability impact.
Summary
What happened
Resource-limit bypass in ImageMagick before 7.1.2-31 and before 6.9.13-56 allows local users to over-allocate memory through scene selection. The PCD, CUBE, and HALD readers clone and append an image for each nonzero scene count without first acquiring the configured list-length resource. Exploitation requires control of command-line options and can exceed the intended memory policy, producing a limited availability impact.
The record
- CVE
- CVE-2026-93587
- Published
- Sep 18, 2026
- Updated
- Sep 18, 2026
- Vendor
- ImageMagick Studio LLC
- Product
- ImageMagick
- Classifications
- CWE-770, CWE-400, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 18, 2026CVE publishedPublication date reported by the CVE source.
- Sep 18, 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-56
- Affected versionversion=0 <7.1.2-31
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started