dbcve.org
ImagemagickApplication

CVE-2026-25987

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, a heap buffer over-read vulnerability exists in the MAP image decoder when processing crafted MAP files, potentially leading to crashes or unintended memory disclosure during image decoding. 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

A heap buffer over-read vulnerability exists in ImageMagick's MAP image decoder when processing crafted MAP files. This can lead to crashes or unintended memory disclosure (potential information disclosure) during image decoding. The vulnerability is present in versions prior to 7.1.2-15 and 6.9.13-40.

MitigationUpgrade ImageMagick to version 7.1.2-15 or later, or 6.9.13-40 or later. If immediate patching is not feasible, consider disabling MAP file format support or implementing input validation for MAP files at the application layer.

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 'magick -version' or 'identify -version' to obtain the installed version number
    Affected if Version is below 6.9.13-40 for the 6.x line, or below 7.1.2-15 for the 7.x line (but 7.0.0-0 or higher)
  2. Verify MAP decoder is available
    Run 'magick -list configure | grep -i map' or check for 'MAP' in the list of supported formats via 'magick -list format'
    Affected if MAP format is listed as supported and loaded
  3. Check MAP file processing capability
    Attempt to identify a sample MAP file (e.g., 'identify sample.map') or check if the MAP coder module exists in the ImageMagick modules directory
    Affected if The MAP decoder can process input files, indicating the vulnerable code path is present
  4. Review ImageMagick policy configuration
    Examine /etc/ImageMagick-6/policy.xml or /etc/ImageMagick-7/policy.xml (or the active policy file) for any restrictions on MAP format
    Affected if MAP format is not explicitly blocked in the security policy, allowing processing of potentially crafted files

A system is affected if it runs ImageMagick version 6.9.13-40 or earlier (6.x line), or version 7.0.0-0 through 7.1.2-14 (7.x line), AND the MAP image decoder is enabled and capable of processing MAP 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 later, or 6.9.13-40 or later. If immediate patching is not feasible, consider disabling MAP file format support or implementing input validation for MAP files at the application layer.

Recommended fix High confidence

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

  1. 1. Identify the currently installed ImageMagick version using 'convert --version' or 'magick --version'
  2. 2. If using ImageMagick 6.x branch (6.9.13-x), upgrade to version 6.9.13-40 or later
  3. 3. If using ImageMagick 7.x branch (7.0.x - 7.1.2-x), upgrade to version 7.1.2-15 or later
  4. 4. On Debian/Ubuntu: Run 'sudo apt-get update && sudo apt-get install imagemagick' to get the latest packaged version
  5. 5. On RHEL/CentOS/Fedora: Run 'sudo dnf update imagemagick' or 'sudo yum update imagemagick'
  6. 6. On macOS with Homebrew: Run 'brew update && brew upgrade imagemagick'
  7. 7. Verify the new version is installed: 'convert --version' or 'magick --version'
  8. 8. Test that ImageMagick functions correctly with your workflows

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