CVE-2025-55160
Imagemagick ≤ 6.9.13-27
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:LSummary
CVE-2025-55160 is a medium-severity Reliance on Undefined, Unspecified, or Implementation-Defined Behavior (CWE-758) vulnerability in Imagemagick Imagemagick. Its CVSS base score is 6.1 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 34th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
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.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-24566
Vulnerability Data
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to versions 6.9.13-27 and 7.1.2-1, there is undefined behavior (function-type-mismatch) in splay tree cloning callback. This results in a deterministic abort under UBSan (DoS in sanitizer…
more
builds), with no crash in a non-sanitized build. This issue has been patched in versions 6.9.13-27 and 7.1.2-1.
- 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 can discover reliance on undefined behavior through cross-platform or stress testing.
Mandating a documented development process and coding standards directly discourages dependence on unspecified behavior.
Engineering principles can require use of only well-defined language and API behaviors during development.
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.
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 can detect some instances of undefined behavior but does not prevent the root weakness.
Secure development life cycle requires defined, portable coding practices that reduce reliance on undefined behavior.
Secure system architecture and engineering principles mandate use of well-specified interfaces and avoid undefined constructs.
Secure coding explicitly prohibits constructs whose behavior is undefined, unspecified or implementation-defined.