dbcve.org
ImagemagickApplication

CVE-2026-53462

MEDIUM · 5.9 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 6.9.13-50 / 7.1.2-25 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable 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 6.9.13-50 and 7.1.2-25, when an allocation fails in CheckPrimitiveExtent this can result in a heap-use-after-free and result in a crash. This issue has been patched in versions 6.9.13-50 and 7.1.2-25.

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 · moderate confidence

A heap-use-after-free vulnerability exists in ImageMagick's CheckPrimitiveExtent function when a memory allocation fails, leading to potential crash. The vulnerability stems from improper memory handling during allocation failure conditions.

MitigationUpgrade ImageMagick to version 6.9.13-50 or 7.1.2-25 or later. In the interim, restrict untrusted image input processing and monitor for anomalous behavior.

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-50>= 7.0.0-0, < 7.1.2-25

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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/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. Identify ImageMagick installation
    Run 'identify -version' or 'convert -version' to see if ImageMagick is installed and get version information
    Affected if Command returns a version number indicating ImageMagick is present
  2. Determine installed version
    Parse the version output from the previous step. For the 6.x branch, look for version like 6.9.13-49 or lower. For the 7.x branch, look for versions between 7.0.0-0 and 7.1.2-24
    Affected if Version is less than 6.9.13-50, or is 7.0.0-0 through 7.1.2-24 (inclusive)
  3. Identify if image processing triggers vulnerable code path
    The vulnerability lies in CheckPrimitiveExtent function which handles primitive image operations. This function is invoked when processing image primitives via the -sketch, -animate, or similar operations that use primitive extent checking
    Affected if Image processing operations that invoke CheckPrimitiveExtent are performed, particularly when memory allocation under pressure may fail

User is affected if ImageMagick is installed with a version in the 6.x branch below 6.9.13-50, or in the 7.x branch from 7.0.0-0 through 7.1.2-24, and performs image processing operations that call CheckPrimitiveExtent.

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-50 / 7.1.2-25 or later
Fixed in 6.9.13-507.1.2-25
Interim mitigation

Upgrade ImageMagick to version 6.9.13-50 or 7.1.2-25 or later. In the interim, restrict untrusted image input processing and monitor for anomalous behavior.

Recommended fix High confidence

ImageMagick 6.9.13-50+ (6.x branch) or 7.1.2-25+ (7.x branch)

  1. Check current ImageMagick version using 'convert -version' or 'magick --version'
  2. For Debian/Ubuntu systems: Run 'sudo apt-get update' then 'sudo apt-get install imagemagick' to get the latest available version
  3. For RHEL/CentOS/Fedora systems: Run 'sudo yum update ImageMagick' or 'sudo dnf update ImageMagick'
  4. For macOS with Homebrew: Run 'brew upgrade imagemagick'
  5. For source compilation: Download version 6.9.13-50 or later from legacy.imagemagick.org or compile from GitHub release 7.1.2-25 or later for the 7.x branch
  6. Verify the fix by running 'convert -version' and confirming the version number meets or exceeds the fixed releases (6.9.13-50 or 7.1.2-25)
Caveat Minor: Some legacy image processing behaviors may have subtle changes; test critical image workflows after upgrade

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-53462 — 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-53462 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