dbcve.org
ImagemagickApplication

CVE-2026-61857

HIGH · 7.5 CVSS v3.1 Published 2026-07-11
Fix available
A fix is available. Upgrade to 6.9.13-51 / 7.1.2-26 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 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 before 7.1.2-26 contains a heap use-after-free vulnerability caused by missing null check when parsing XMP profiles. Attackers can craft malicious image files with specially crafted XMP data to trigger the vulnerability and cause application crashes.

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 versions before 7.1.2-26 have a heap use-after-free vulnerability in XMP profile parsing due to a missing null check. Attackers can exploit this by embedding specially crafted XMP data in image files, leading to application crashes or potential code execution.

MitigationUpgrade ImageMagick to version 7.1.2-26 or later to receive the patch. If immediate patching is not feasible, disable XMP metadata processing or validate image files before processing.

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
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 installed ImageMagick version
    Run 'identify -version' or 'magick -version' to display the installed version number
    Affected if The version displayed is below 6.9.13-51, or is 7.0.0-0 through 7.1.2-25 (any version less than 7.1.2-26)
  2. Verify XMP metadata parsing is active
    Inspect ImageMagick policy.xml file (typically at /etc/ImageMagick-6/policy.xml or /etc/ImageMagick/policy.xml) and look for any 'XMP' or 'xml' coder restrictions. Also check if identify or convert commands can extract XMP data from a test image using 'identify -verbose testimage'
    Affected if The policy.xml does not restrict XMP/xml coders, or XMP metadata appears in verbose output - meaning the system processes XMP data
  3. Determine if untrusted image files are processed
    Review application logs, web server configs, or automation scripts that invoke ImageMagick to see if external or user-uploaded images are processed
    Affected if ImageMagick processes image files from untrusted sources such as web uploads, email attachments, or external API calls

You are affected if your installed ImageMagick version falls in the vulnerable ranges AND your system processes XMP metadata from untrusted image files.

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 7.1.2-26 or later to receive the patch. If immediate patching is not feasible, disable XMP metadata processing or validate image files before processing.

Recommended fix Moderate confidence

Upgrade to ImageMagick 6.9.13-51+ (6.x branch) or 7.1.2-26+ (7.x branch)

  1. Check the currently installed ImageMagick version using 'convert -version' or 'magick -version'
  2. For systems using the 6.x branch: upgrade to version 6.9.13-51 or later (e.g., 6.9.13-51, 6.9.14-x, etc.)
  3. For systems using the 7.x branch: upgrade to version 7.1.2-26 or later (e.g., 7.1.2-26, 7.1.3-x, etc.)
  4. On RHEL/CentOS/Fedora: run 'sudo yum update ImageMagick' or 'sudo dnf update ImageMagick'
  5. On Debian/Ubuntu: run 'sudo apt-get update && sudo apt-get install imagemagick'
  6. On macOS with Homebrew: run 'brew upgrade imagemagick'
  7. Verify the fix was applied by running 'convert -version' and confirming the version number meets the fixed releases
  8. Restart any services that use ImageMagick to ensure the patched library is loaded
Caveat Minor: Some legacy image processing behaviors may have changed; 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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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