Heap-byte disclosure via PCD decoder over-read
Published Jun 21, 2026 · Updated Jun 21, 2026
Out-of-bounds read in ImageMagick before 7.1.2-15 and 6.x before 6.9.13-40 allows remote attackers to disclose one heap byte. The PCD coder's DecodeImage loop advances one byte beyond its heap buffer while decoding a crafted PCD image. Processing attacker-supplied PCD content without user interaction exposes an adjacent heap byte and can interrupt image decoding.
Summary
What happened
Out-of-bounds read in ImageMagick before 7.1.2-15 and 6.x before 6.9.13-40 allows remote attackers to disclose one heap byte. The PCD coder's DecodeImage loop advances one byte beyond its heap buffer while decoding a crafted PCD image. Processing attacker-supplied PCD content without user interaction exposes an adjacent heap byte and can interrupt image decoding.
The record
- CVE
- CVE-2026-56378
- Published
- Jun 21, 2026
- Updated
- Jun 21, 2026
- Vendor
- ImageMagick Studio LLC
- Product
- ImageMagick
- Classifications
- CWE-125
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 21, 2026CVE publishedPublication date reported by the CVE source.
- Jun 21, 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-40
- Affected versionversion=0 <7.1.2-15
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