dbcve.org
ImagemagickApplication

CVE-2026-46523

MEDIUM · 6.2 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 6.9.13-48 / 7.1.2-23 or later.
See remediation →
67/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

ImageMagick contains a heap-use-after-free vulnerability when processing specially crafted MSL (Magick Scripting Language) image files. This memory safety issue in versions prior to 7.1.2.23 and 6.9.13-48 could allow remote attackers to cause denial of service or potentially execute arbitrary code via a malicious MSL file.

MitigationUpgrade ImageMagick to version 7.1.2.23 or later (7.x branch) or 6.9.13-48 or later (6.x branch). As a compensating control, consider disabling MSL script processing if immediate upgrade is not feasible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ImagemagickApplication
Affected:< 6.9.13-48>= 7.0.0-0, < 7.1.2-23

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed ImageMagick version
    Run `identify -version` or `magick -version` to retrieve the installed version number
    Affected if Version is below 6.9.13-48 (6.x branch) or below 7.1.2-23 (7.x branch)
  2. Identify ImageMagick configuration file location
    Run `identify -list configure` to find the configuration directory path (typically /etc/ImageMagick-6 or /etc/ImageMagick-7)
    Affected if Configuration directory exists and contains policy.xml or coder.xml files
  3. Verify if MSL script processing is enabled
    Search for MSL-related entries in policy.xml: grep -i 'msl' /etc/ImageMagick-*/policy.xml or check coder.xml for MSL coder presence
    Affected if MSL is not explicitly disabled or restricted in the policy configuration
  4. Check ImageMagick delegate configuration for MSL
    Run `identify -list delegate` or examine delegates.xml in the configuration directory for 'msl' entries that enable script processing
    Affected if MSL delegate is present and active in the delegate configuration

A system is affected if it runs a vulnerable ImageMagick version AND has MSL script processing enabled, allowing specially crafted MSL files to trigger the heap-use-after-free.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.9.13-48 / 7.1.2-23 or later
Fixed in 6.9.13-487.1.2-23
Interim mitigation

Upgrade ImageMagick to version 7.1.2.23 or later (7.x branch) or 6.9.13-48 or later (6.x branch). As a compensating control, consider disabling MSL script processing if immediate upgrade is not feasible.

Recommended fix High confidence

ImageMagick 6.9.13-48 or 7.1.2-23 (whichever branch is in use)

  1. 1. Check the current ImageMagick version by running 'convert -version' or 'magick -version'
  2. 2. If using the 6.x branch (versions < 6.9.13-48), upgrade to version 6.9.13-48 or later
  3. 3. If using the 7.x branch (versions >= 7.0.0-0 and < 7.1.2-23), upgrade to version 7.1.2-23 or later
  4. 4. Use your system's package manager (e.g., apt, yum, dnf) or compile from source to obtain the fixed version
  5. 5. Verify the upgrade was successful by running 'convert -version' and confirming the installed version matches or exceeds the fixed release

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Imagemagick Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-46523 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-46523 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data