dbcve.org
ImagemagickApplication

CVE-2026-53460

HIGH · 7.5 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 →
84/100
Remediation priority · High
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, a missing check for maximum memory request in AcquireAlignedMemory could trigger an out-of-Memory condition. 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 · high confidence

A missing bounds check in ImageMagick's AcquireAlignedMemory function allows attackers to request excessive memory allocations without validation. By crafting images that trigger large memory requests, attackers can cause an out-of-Memory condition leading to denial of service.

MitigationUpgrade ImageMagick to version 6.9.13-50 or 7.1.2-25 or later. If immediate patching is not feasible, implement memory usage limits and process isolation to constrain the impact of excessive memory requests.

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

CVSS:3.1/AV:N/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 if ImageMagick is installed
    Run 'convert -version' or 'magick -version' on the command line
    Affected if The command returns a version number indicating ImageMagick is present
  2. Identify the installed ImageMagick version and branch
    Examine the output from the version command - look for a version like 6.9.x for the 6.x branch or 7.0.x/7.1.x for the 7.x branch
    Affected if A version number is returned from the version command
  3. Compare version against affected ranges for 6.x branch
    If using ImageMagick 6.x, check if the version is earlier than 6.9.13-50
    Affected if Version is less than 6.9.13-50 (for example, 6.9.13-0 through 6.9.13-49 would be affected)
  4. Compare version against affected ranges for 7.x branch
    If using ImageMagick 7.x, check if the version is 7.0.0-0 or later but earlier than 7.1.2-25
    Affected if Version is 7.0.0-0 or later but earlier than 7.1.2-25 (for example, 7.0.0-0 through 7.1.2-24 would be affected)

You are affected if ImageMagick is installed and the version falls below 6.9.13-50 in the 6.x branch, or between 7.0.0-0 and 7.1.2-24 in the 7.x branch.

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. If immediate patching is not feasible, implement memory usage limits and process isolation to constrain the impact of excessive memory requests.

Recommended fix High confidence

ImageMagick 6.9.13-50 or 7.1.2-25 (depending on your branch)

  1. Check current ImageMagick version using 'convert -version' or 'magick --version'
  2. Identify whether you are using the 6.x or 7.x branch
  3. For systems using package managers, update using: 'yum update ImageMagick' (RHEL/CentOS) or 'apt-get update && apt-get install imagemagick' (Debian/Ubuntu)
  4. Alternatively, download source from ImageMagick official repository and compile versions 6.9.13-50 or 7.1.2-25
  5. Verify the upgrade was successful by checking the new version with 'convert -version'
  6. Test critical image processing workflows to ensure functionality is intact

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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