dbcve.org
ImagemagickApplication

CVE-2026-55510

MEDIUM · 5.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 →
58/100
Remediation priority · Elevated
No privileges 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, when identifying an image with a crafted 8BIM profile with a specific format string a use-after-free will occur. 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 · moderate confidence

ImageMagick contains a use-after-free vulnerability in its image identification functionality when parsing a crafted 8BIM profile (commonly used in Photoshop images). The specific format string within the 8BIM metadata triggers memory corruption during the identify operation, leading to use-after-free. This is a memory corruption bug that could potentially be leveraged for code execution depending on heap layout and memory reuse patterns.

MitigationUpgrade to ImageMagick versions 6.9.13-51 (ImageMagick 6 series) or 7.1.2-26 (ImageMagick 7 series) or later. If immediate upgrade is not feasible, restrict processing of untrusted image files, particularly those that may contain 8BIM metadata, and disable the identify coder or use sandboxing.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 'convert -version' to retrieve the version number
    Affected if Version is below 6.9.13-51 for the 6.x series, or below 7.1.2-26 for the 7.x series
  2. Confirm identify command availability
    Run 'which identify' or 'identify -list configure' to verify the identify binary is present
    Affected if The identify command is available and operational
  3. Verify 8BIM profile parser is enabled
    Run 'identify -list coder' and check if formats that may contain 8BIM metadata (such as PSD, TIFF, JPEG with EXIF) can be read
    Affected if Coders capable of processing 8BIM metadata are enabled
  4. Check for loaded image processing modules
    Run 'identify -list module' to enumerate loaded modules
    Affected if Modules related to image identification are loaded and active
  5. Test identify operation on a sample image
    Run 'identify <imagefile>' on any sample image to confirm the identify functionality works
    Affected if The identify command executes without errors, confirming the vulnerable code path is present

You are affected if your ImageMagick version is below 6.9.13-51 (6.x series) or below 7.1.2-26 (7.x series) AND you have the identify functionality enabled to process images containing 8BIM metadata.

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 to ImageMagick versions 6.9.13-51 (ImageMagick 6 series) or 7.1.2-26 (ImageMagick 7 series) or later. If immediate upgrade is not feasible, restrict processing of untrusted image files, particularly those that may contain 8BIM metadata, and disable the identify coder or use sandboxing.

Recommended fix High confidence

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

  1. 1. Check current ImageMagick version by running 'convert --version' or 'magick --version'
  2. 2. If using ImageMagick 6.x branch (version < 6.9.13-51), upgrade to version 6.9.13-51 or later using your package manager (e.g., 'apt update && apt install imagemagick' on Debian/Ubuntu, or 'yum update ImageMagick' on RHEL/CentOS)
  3. 3. If using ImageMagick 7.x branch (version >= 7.0.0 and < 7.1.2-26), upgrade to version 7.1.2-26 or later using your package manager
  4. 4. Verify the upgrade was successful by running 'convert --version' or 'magick --version' to confirm the installed version matches or exceeds the fixed release
  5. 5. Test any image processing workflows that involve 8BIM profiles to ensure normal operation
Caveat Minor - patch releases typically contain only bug fixes; review ImageMagick release notes for any behavioral changes

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
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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