PatchSiren cyber security CVE debrief
CVE-2026-61868 ImageMagick CVE debrief
ImageMagick before 7.1.2-26 and 6.9.x before 6.9.13-51 contains a memory leak in the YUV decoder that occurs when opening of the blob fails. Repeated triggering can lead to resource exhaustion (denial of service). The vulnerability affects ImageMagick installations, particularly those using versions before 7.1.2-26 and 6.9.x before 6.9.13-51. Defenders should assess exposure and prioritize patching to prevent potential resource exhaustion and system performance degradation. The memory leak can result in denial of service if repeatedly triggered, emphasizing the need for verification of ImageMagick versions and patching.
- Vendor
- ImageMagick
- Product
- Unknown
- CVSS
- MEDIUM 6.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-15
- Original CVE updated
- 2026-10-29
- Advisory published
- 2026-07-15
- Advisory updated
- 2026-10-29
Who should care
Defenders responsible for ImageMagick installations, particularly those using versions before 7.1.2-26 and 6.9.x before 6.9.13-51, should assess exposure and prioritize patching.
Why it matters
Defenders should care about CVE-2026-61868 because it involves a memory leak in ImageMagick that can lead to denial of service. Those responsible for ImageMagick installations, especially in versions before 7.1.2-26 and 6.9.x before 6.9.13-51, should assess exposure and prioritize patching to prevent potential resource exhaustion and system performance degradation.
- Denial of service through resource exhaustion
- Potential for significant system performance degradation
- Need for verification of ImageMagick versions and patching
- Possible impact on services relying on ImageMagick
Technical summary
The vulnerability occurs in the YUV decoder of ImageMagick, leading to a memory leak when opening a blob fails. This can result in resource exhaustion and denial of service if repeatedly triggered. The vulnerability affects ImageMagick installations, particularly those using versions before 7.1.2-26 and 6.9.x before 6.9.13-51. Defenders should prioritize verifying ImageMagick versions and updating to patched versions if vulnerable to prevent potential resource exhaustion and system performance degradation.
Defensive priority
Defenders should prioritize verifying ImageMagick versions and updating to patched versions if vulnerable.
Recommended defensive actions
- Verify ImageMagick versions in use and update to patched versions if vulnerable
- Monitor for repeated triggering of the YUV decoder that could lead to resource exhaustion
- Implement compensating controls to mitigate potential denial of service
Evidence notes
The CVE record and NVD entry provide details on the memory leak vulnerability in ImageMagick. The vulnerability occurs in the YUV decoder of ImageMagick, leading to a memory leak when opening a blob fails. This can result in resource exhaustion and denial of service if repeatedly triggered. The official CVE Program record and NVD detail page offer source-provided CVE metadata and vulnerability assessments. Additional source references are available from Vulncheck advisory on ImageMagck
Sources and references
Verified primary and authoritative sources
-
CVE-2026-61868 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-61868
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-61868 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-61868
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/ImageMagick/ImageMagick/security/advisories/GHSA-h7f2-f9cc-h2gv
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/imagemagick-before-26-memory-leak-in-yuv-decoder
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.