CVE-2026-25986
Memory Safety in Imagemagick ≤ 6.9.13-40
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LSummary
CVE-2026-25986 is a medium-severity Out-of-bounds Write (CWE-787) vulnerability in Imagemagick Imagemagick. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-25986 is a heap buffer overflow write vulnerability (CWE-787) in ImageMagick, a free and open-source software suite for editing and manipulating digital images. It affects all versions prior to 7.1.2-15 and 6.9.13-40, specifically in the ReadYUVImage() function within coders/yuv.c. The flaw occurs when processing malicious YUV 4:2:2 (NoInterlace) images, where a pixel-pair loop writes one pixel beyond the allocated row buffer, potentially leading to heap corruption.
The vulnerability carries a CVSS v3.1 base score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L), indicating network accessibility with low attack complexity, no required privileges or user interaction, and unchanged impact scope. Remote attackers can exploit it by supplying a crafted YUV image to an ImageMagick-based application or service, achieving limited denial-of-service effects such as application crashes or resource exhaustion due to the buffer overflow, without compromising confidentiality or integrity.
The official ImageMagick GitHub security advisory (GHSA-mqfc-82jx-3mr2) documents the issue and confirms that patches addressing the out-of-bounds write are included in versions 7.1.2-15 and 6.9.13-40. Security practitioners should prioritize upgrading affected ImageMagick installations to these patched versions and validate image inputs where possible to prevent exploitation.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-7420
Vulnerability Data
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to versions 7.1.2-15 and 6.9.13-40, a heap buffer overflow write vulnerability exists in ReadYUVImage() (coders/yuv.c) when processing malicious YUV 4:2:2 (NoInterlace) images. The pixel-pair loop writes…
more
one pixel beyond the allocated row buffer. Versions 7.1.2-15 and 6.9.13-40 contain a patch.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.
Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.
Input validation can structurally reject or sanitize data that would otherwise trigger an out-of-bounds write.
Memory-protection mechanisms limit the exploitability and blast radius of a successful out-of-bounds write.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect and prevent out-of-bounds write defects.
Secure development life cycle mandates practices that prevent out-of-bounds writes.
Application security requirements can specify bounds-checking and safe memory handling.
Secure architecture and engineering principles reduce the likelihood of buffer overflows.
Secure coding directly addresses out-of-bounds writes through language choice and coding standards.
Change management can enforce review gates that catch unsafe memory operations before deployment.