dbcve.org
ImagemagickApplication

CVE-2026-53466

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 6.9.13-51 / 7.1.2-26 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 7 weeks old

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-51 and 7.1.2-26, an integer overflow in the XCF decoder can result in an out of bounds read when a crafted image is read, potentially resulting in a crash. This issue has been fixed in versions 6.9.13-51 and 7.1.2-26.

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

An integer overflow vulnerability exists in ImageMagick's XCF (native GIMP format) decoder. When processing a specially crafted XCF image file, the integer overflow leads to an out-of-bounds memory read, which can cause the application to crash. The vulnerability is triggered during image parsing before any display or processing occurs.

MitigationUpgrade ImageMagick to version 6.9.13-51 or 7.1.2-26 or later. If upgrading is not immediately possible, disable XCF format support or implement input validation to reject untrusted XCF files.

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

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
Low
Integrity
None
Availability
Low

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

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. Determine installed ImageMagick version
    Run 'convert --version' (ImageMagick 6) or 'magick --version' (ImageMagick 7) and note the version number shown in the output.
    Affected if The version is less than 6.9.13-51, or is 7.0.0-0 through 7.1.2-25 (inclusive).
  2. Confirm XCF format support is available
    Run 'convert -list format' (ImageMagick 6) or 'magick -list format' (ImageMagick 7) and search for XCF in the output. Look for a line showing 'XCF*' with read support (the asterisk indicates native support).
    Affected if XCF format is listed with read capability (R) enabled in the supported formats.
  3. Verify XCF coder module exists
    Check for the presence of the XCF-related coder file. Common locations: 'coders/xcf.c' in source, 'lib/ImageMagick-*/coders/XCF.so' or 'C:\Program Files\ImageMagick-*/modules-Q16/coders/XCF.dll' depending on OS and installation path.
    Affected if The XCF coder module file exists and is loadable by ImageMagick.
  4. Test XCF file processing capability
    Attempt to identify an XCF file using ImageMagick: 'identify <file.xcf>' where <file.xcf> is any XCF file, or use 'identify -list format' to confirm XCF is recognized as a read-enabled format.
    Affected if ImageMagick can read and identify XCF files without explicit disablement.

A user is affected if they have ImageMagick version 6.9.13-51 or earlier (6.x), or version 7.0.0-0 through 7.1.2-25 (7.x), AND XCF format support is enabled in their ImageMagick installation.

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

Upgrade ImageMagick to version 6.9.13-51 or 7.1.2-26 or later. If upgrading is not immediately possible, disable XCF format support or implement input validation to reject untrusted XCF files.

Recommended fix High confidence

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

  1. Check current ImageMagick version using 'convert --version' or 'magick --version'
  2. If using ImageMagick 6.x branch (6.x.x), upgrade to version 6.9.13-51 or later using your system's package manager (e.g., apt-get update && apt-get install imagemagick, yum update imagemagick, etc.)
  3. If using ImageMagick 7.x branch (7.x.x), upgrade to version 7.1.2-26 or later
  4. After upgrade, verify the new version is installed with 'convert --version' or 'magick --version'
  5. Test that ImageMagick functions correctly with your workflows
Caveat Minor version upgrades may include behavioral changes; test critical image processing workflows after upgrading

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-53466 — 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-53466 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