dbcve.org
ImagemagickApplication

CVE-2026-25897

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-24
Fix available
A fix is available. Upgrade to 6.9.13-40 / 7.1.2-15 or later.
See remediation →
100/100
Remediation priority · Urgent
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 7.1.2-15 and 6.9.13-40, an Integer Overflow vulnerability exists in the sun decoder. On 32-bit systems/builds, a carefully crafted image can lead to an out of bounds heap write. Versions 7.1.2-15 and 6.9.13-40 contain a patch.

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 in ImageMagick's sun image format decoder allows specially crafted SUN images to trigger heap memory corruption on 32-bit systems. The overflow occurs during image processing calculations, enabling potential remote code execution.

MitigationUpgrade ImageMagick to version 7.1.2-15/6.9.13-40 or later. On 64-bit systems the impact is reduced but upgrading is still recommended.

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

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. Confirm ImageMagick installation and version
    Run `identify -version` or `magick -version` to obtain the installed ImageMagick version number
    Affected if The version displayed is less than 6.9.13-40 for the 6.x series, or between 7.0.0-0 and 7.1.2-14 for the 7.x series
  2. Identify system architecture
    Run `uname -m` or check system documentation to determine if the system is 32-bit (i386/i686) or 64-bit (x86_64)
    Affected if The system is 32-bit; 64-bit systems have reduced impact from this vulnerability
  3. Check if SUN image format decoder is available
    Run `identify -list format` and look for SUN in the output, or attempt to identify a test SUN file with `identify test.sun`
    Affected if The SUN format is listed as supported and can be processed by ImageMagick; the vulnerability only applies when ImageMagick can decode SUN images
  4. Verify active coders configuration
    Check /etc/ImageMagick-6/coder.xml or /etc/ImageMagick-7/coder.xml (or the equivalent path in your environment) for the SUN coder entry
    Affected if The SUN coder is present and not disabled in the ImageMagick coder configuration

You are affected if ImageMagick is installed with a vulnerable version (6.x < 6.9.13-40 or 7.x < 7.1.2-15), the SUN image decoder is enabled, and processing of untrusted SUN files is possible on a 32-bit system.

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-40 / 7.1.2-15 or later
Fixed in 6.9.13-407.1.2-15
Interim mitigation

Upgrade ImageMagick to version 7.1.2-15/6.9.13-40 or later. On 64-bit systems the impact is reduced but upgrading is still recommended.

Recommended fix High confidence

Upgrade to ImageMagick 7.1.2-15 or later for version 7.x, or 6.9.13-40 or later for version 6.x

  1. Identify current ImageMagick version using 'convert --version' or 'magick --version'
  2. For Debian/Ubuntu systems: run 'sudo apt-get update' then 'sudo apt-get install imagemagick'
  3. For RHEL/CentOS/Fedora systems: run 'sudo yum update ImageMagick' or 'sudo dnf update ImageMagick'
  4. For Alpine systems: run 'apk update' then 'apk upgrade imagemagick'
  5. Verify the installed version matches or exceeds 7.1.2-15 (for 7.x) or 6.9.13-40 (for 6.x) using 'convert --version'
  6. Test ImageMagick functionality with your image processing workflows before deploying to production
Caveat Minimal risk - patch releases typically contain only bug and security fixes; however, test in non-production first

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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