Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:HSummary
CVE-2026-55597 is a medium-severity Incorrect Calculation (CWE-682) vulnerability in Imagemagick Imagemagick. Its CVSS base score is 5.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked at the 1th 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 SI-2 (Flaw Remediation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-41124
Vulnerability Data
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to version 7.1.2-26, an incorrect handling of arguments can cause a heap buffer over-write in the JP2 encoder. This issue has been fixed in version7.1.2-26.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Heap buffer overwrite in image encoder enables client-side code execution via malicious JP2 image files.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly requires applying the vendor patch (7.1.2-26) that corrects the argument-handling flaw and eliminates the heap buffer overwrite.
Mandates validation of all inputs to the JP2 encoder, blocking malformed arguments that trigger the incorrect calculation (CWE-682) and subsequent out-of-bounds write.
Requires integrity verification of ImageMagick binaries and libraries, enabling detection of unauthorized memory modifications caused by the buffer overwrite.
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 SDLC practices directly prevent incorrect calculations via reviews, testing, and verification in security-critical code.
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 calculation flaws before deployment.
Secure development lifecycle mandates verification steps that catch incorrect calculations before they reach production.
Application security requirements can explicitly call for numeric accuracy and bounds checking.
Secure architecture principles include input validation and safe arithmetic design that reduce calculation errors.
Secure coding standards directly prohibit unsafe arithmetic and require defensive checks against incorrect results.
Change management can enforce review gates that catch unsafe memory operations before deployment.