dbcve.org
ImagemagickApplication

CVE-2025-53014

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-14
Fix available
A fix is available. Upgrade to 6.9.13-26 / 7.1.2-0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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. Versions prior to 7.1.2-0 and 6.9.13-26 have a heap buffer overflow in the `InterpretImageFilename` function. The issue stems from an off-by-one error that causes out-of-bounds memory access when processing format strings containing consecutive percent signs (`%%`). Versions 7.1.2-0 and 6.9.13-26 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 buffer overflow vulnerability in the InterpretImageFilename function caused by an off-by-one error. The flaw triggers out-of-bounds memory access when processing format strings containing consecutive percent signs (%%), leading to potential heap corruption and possible remote code execution.

MitigationUpgrade ImageMagick to version 7.1.2-0 or 6.9.13-26 or later to resolve the heap buffer overflow. If immediate patching is not feasible, consider disabling or restricting ImageMagick image processing capabilities for untrusted inputs.

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

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 'convert -version' or 'magick -version' and record the version number displayed
    Affected if Version is 6.x and less than 6.9.13-26, or version is 7.x and less than 7.1.2-0
  2. Confirm which ImageMagick binary is in use
    Run 'which convert' or 'which magick' to find the executable path, then run the version command from that path
    Affected if Multiple ImageMagick installations exist and the vulnerable version is being used
  3. Identify use of InterpretImageFilename functionality
    Search ImageMagick usage in scripts, applications, or web interfaces for format strings or filename patterns that use percent signs
    Affected if ImageMagick processes filenames or format strings containing consecutive percent signs (%%)
  4. Review application input handling for ImageMagick
    Examine how user-supplied filenames or format parameters are passed to ImageMagick, looking for patterns that could include %% sequences
    Affected if User-controlled input reaches ImageMagick filename interpretation without sanitization of percent characters

Environment is affected if the installed ImageMagick version falls within the vulnerable ranges AND the system processes image filenames or format strings with consecutive percent signs through the InterpretImageFilename function.

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-26 / 7.1.2-0 or later
Fixed in 6.9.13-267.1.2-0
Interim mitigation

Upgrade ImageMagick to version 7.1.2-0 or 6.9.13-26 or later to resolve the heap buffer overflow. If immediate patching is not feasible, consider disabling or restricting ImageMagick image processing capabilities for untrusted inputs.

Recommended fix High confidence

ImageMagick 6.9.13-26 (for 6.x branch) or ImageMagick 7.1.2-0 (for 7.x branch)

  1. Identify your current ImageMagick version using 'convert -version' or 'magick -version'
  2. If running ImageMagick 6.x (e.g., 6.9.x): upgrade to version 6.9.13-26 or later
  3. If running ImageMagick 7.x (e.g., 7.0.x or 7.1.x): upgrade to version 7.1.2-0 or later
  4. Use your system's package manager (apt, yum, dnf, brew, etc.) to install the updated package, e.g., 'apt-get update && apt-get install imagemagick' or 'sudo yum update imagemagick'
  5. Verify the installed version matches or exceeds the fixed release using 'convert -version'
Caveat Standard upgrade; ImageMagick maintains backward compatibility within major versions; verify any custom image processing scripts work after upgrade

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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