Cyber Resilience

CVE-2026-46523

Memory Safety in Imagemagick ≤ 6.9.13-48

Published
10 June 2026
Modified
15 July 2026
Patch / advisory
CVSS Score v3.1 6.2
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0030 22th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-46523 is a medium-severity Use After Free (CWE-416) vulnerability in Imagemagick Imagemagick. Its CVSS base score is 6.2 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 22th 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

Vulnerability Data

ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to versions 7.1.2.23 and 6.9.13-48, a crafted MSL image can trigger a heap-use-after-free. Versions 7.1.2.23 and 6.9.13-48 fix the issue.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1204.003 Malicious Image Execution
Adversaries may rely on a user running a malicious image to facilitate execution.
Why these techniques?

Use-after-free in ImageMagick image processing enables RCE via crafted MSL images, directly facilitating server-side exploitation (T1190) or malicious image delivery (T1204.003).

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-25983Same product: Imagemagick Imagemagick
CVE-2026-28687Same product: Imagemagick Imagemagick
CVE-2026-55510Same product: Imagemagick Imagemagick
CVE-2026-56373Same product: Imagemagick Imagemagick
CVE-2026-61861Same product: Imagemagick Imagemagick
CVE-2026-53462Same product: Imagemagick Imagemagick
CVE-2026-28688Same product: Imagemagick Imagemagick
CVE-2026-56376Same product: Imagemagick Imagemagick
CVE-2026-26983Same product: Imagemagick Imagemagick
CVE-2025-65955Same product: Imagemagick Imagemagick

Affected Assets

imagemagick
imagemagick
≤ 6.9.13-48 · 7.0.0-0 — 7.1.2-23

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-2 Flaw Remediation
  • SI-10 Information Input Validation
Detect
Catch it (NIST detect / respond)
  • SI-7 Software, Firmware, and Information Integrity
Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V1.4.3

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires applying the vendor patch that eliminates the heap use-after-free in MSL processing.

prevent

Input validation on image files can reject or sanitize malformed MSL content before it reaches the vulnerable parser.

detect

Integrity verification of ImageMagick binaries and libraries can detect unauthorized or tampered versions containing the flaw.

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly incorporate memory-safety tooling and reviews that prevent most use-after-free defects.

ID.AM-08 partial match
prevents

Lifecycle management includes secure development and maintenance phases that reduce memory-safety defects.

ID.RA-01 partial match
prevents

Vulnerability identification processes can discover use-after-free issues via scanning or analysis but do not prevent their introduction.

PR.PS-02 partial match
prevents

Routine patching removes known use-after-free instances after they have been introduced in released software.

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.

detects

Security testing in development can detect use-after-free bugs before release.

prevents

Secure SDLC mandates memory-safety practices that reduce use-after-free defects.

prevents

Application security requirements can specify memory-management rules that mitigate use-after-free.

prevents

Secure architecture principles include memory-safety design choices that limit use-after-free exposure.

prevents

Secure coding standards directly prescribe avoidance of use-after-free patterns.

prevents

Change-management processes help ensure memory-safety fixes are deployed consistently.

References