Process-memory exhaustion via unreleased ASHLAR drawing state
Published Feb 24, 2026 · Updated Feb 24, 2026
Memory exhaustion in ImageMagick's ASHLAR writer before 7.1.2-15 allows remote attackers to interrupt processing with crafted images. ASHLARImage cloned DrawInfo before confirming that a label existed and failed to destroy that state after annotation, leaking allocations for small objects. A reachable workflow must write attacker-supplied images as ASHLAR output; repeated processing consumes process memory without disclosing or altering data.
Summary
What happened
Memory exhaustion in ImageMagick's ASHLAR writer before 7.1.2-15 allows remote attackers to interrupt processing with crafted images. ASHLARImage cloned DrawInfo before confirming that a label existed and failed to destroy that state after annotation, leaking allocations for small objects. A reachable workflow must write attacker-supplied images as ASHLAR output; repeated processing consumes process memory without disclosing or altering data.
The record
- CVE
- CVE-2026-25637
- Published
- Feb 24, 2026
- Updated
- Feb 24, 2026
- Vendor
- ImageMagick Studio LLC
- Product
- ImageMagick
- Classifications
- CWE-401, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 24, 2026CVE publishedPublication date reported by the CVE source.
- Feb 24, 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=< 7.1.2-15
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