dbcve.org
ImagemagickApplication

CVE-2026-25898

CRITICAL · 9.1 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, the UIL and XPM image encoder do not validate the pixel index value returned by `GetPixelIndex()` before using it as an array subscript. In HDRI builds, `Quantum` is a floating-point type, so pixel index values can be negative. An attacker can craft an image with negative pixel index values to trigger a global buffer overflow read during conversion, leading to information disclosure or a process crash. 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

ImageMagick's UIL and XPM image encoders fail to validate the pixel index value returned by GetPixelIndex() before using it as an array subscript. In HDRI builds where Quantum is a floating-point type, this allows negative index values. Crafted images with negative pixel index values cause a global buffer overflow read, leading to information disclosure or process crash.

MitigationUpgrade ImageMagick to version 7.1.2-15 or 6.9.13-40 or later. If upgrading is not immediately possible, disable or avoid processing untrusted UIL and XPM image files, especially in HDRI configurations.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 'convert -version' or 'magick -version' and look for the version number in the output (e.g., 6.9.13-40 or 7.1.2-15)
    Affected if Version is below 6.9.13-40 OR version is 7.0.0-0 through 7.1.2-14
  2. Confirm HDRI support is enabled
    Run 'convert -list configure | grep -i hdi' or check 'magick -list configure' for HDRI-related flags. On some systems, 'identify -list Configure' shows 'HDRI' as enabled.
    Affected if HDRI support is present (Quantum is a floating-point type in HDRI builds)
  3. Verify UIL and XPM coders are available
    Run 'convert -list coder' or 'magick -list coder' and look for 'UIL' and 'XPM' in the list of supported formats
    Affected if Both UIL and XPM coders are present in the ImageMagick installation

You are affected if your ImageMagick version falls within the vulnerable range AND HDRI is enabled AND UIL/XPM coders are available to process crafted 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-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 or 6.9.13-40 or later. If upgrading is not immediately possible, disable or avoid processing untrusted UIL and XPM image files, especially in HDRI configurations.

Recommended fix High confidence

ImageMagick 6.9.13-40 (6.x branch) or ImageMagick 7.1.2-15 (7.x branch)

  1. Identify your current ImageMagick version using `convert --version` or `magick --version`
  2. If running ImageMagick 6.x (version < 6.9.13-40), upgrade to version 6.9.13-40 or later
  3. If running ImageMagick 7.x (version < 7.1.2-15), upgrade to version 7.1.2-15 or later
  4. On Debian/Ubuntu: Run `sudo apt-get update && sudo apt-get install imagemagick` or specify version with `sudo apt-get install imagemagick=6:6.9.13-40-*`
  5. On RHEL/CentOS: Run `sudo yum update ImageMagick` or `sudo dnf update ImageMagick`
  6. On macOS with Homebrew: Run `brew upgrade imagemagick`
  7. Verify the upgrade was successful by checking the version with `convert --version`
  8. Test any image processing workflows that use UIL or XPM image formats to confirm functionality

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation3.0 h
  • Implementation5.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,460
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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