dbcve.org
ImagemagickApplication

CVE-2026-25985

HIGH · 7.5 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 →
84/100
Remediation priority · High
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 crafted SVG file containing an malicious element causes ImageMagick to attempt to allocate ~674 GB of memory, leading to an out-of-memory abort. 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 versions prior to 7.1.2-15 and 6.9.13-40 contain a memory allocation vulnerability where a crafted SVG file with a malicious element triggers an attempt to allocate approximately 674 GB of memory, causing an out-of-memory abort. This is a denial-of-service vulnerability exploitable through malicious SVG input.

MitigationUpgrade ImageMagick to version 7.1.2-15 / 6.9.13-40 or later to apply the patch. Consider restricting or disabling SVG processing in ImageMagick configurations if not required, and implement memory limits for image processing as an additional defense 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
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. Verify ImageMagick is installed
    Run 'magick -version' or 'identify -version' to confirm ImageMagick is present on the system
    Affected if The command returns a version number indicating ImageMagick is installed
  2. Determine the installed ImageMagick version
    Parse the output from 'magick -version' to identify the exact version number (for example, 7.1.1-14 or 6.9.12-30)
    Affected if The installed version is displayed and can be compared against the affected ranges
  3. Confirm SVG file handling is available
    Run 'magick -list configure | grep DELEGATES' or check for the SVG coder by running 'magick identify -list coder' to see if SVG support is enabled
    Affected if SVG is listed as an available delegate or coder, meaning the vulnerability could be triggered
  4. Compare version against affected ranges
    Check if the installed version is less than 6.9.13-40, OR is 7.0.0-0 or higher but less than 7.1.2-15
    Affected if The installed version falls below 6.9.13-40, or is between 7.0.0-0 and 7.1.2-14 inclusive

The system is affected if ImageMagick is installed with SVG support enabled and the version is either below 6.9.13-40 or between 7.0.0-0 and 7.1.2-14 inclusive.

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 to apply the patch. Consider restricting or disabling SVG processing in ImageMagick configurations if not required, and implement memory limits for image processing as an additional defense layer.

Recommended fix High confidence

ImageMagick 6.9.13-40+ or 7.1.2-15+ (depending on your major version branch)

  1. 1. Identify your current ImageMagick version using 'convert --version' or 'magick --version'
  2. 2. Determine which major version branch you are using (6.x or 7.x)
  3. 3. For ImageMagick 6.x users: upgrade to version 6.9.13-40 or later
  4. 4. For ImageMagick 7.x users: upgrade to version 7.1.2-15 or later
  5. 5. Upgrade using your system's package manager (e.g., 'apt-get update && apt-get install imagemagick', 'yum update ImageMagick', or compile from source)
  6. 6. Verify the upgrade was successful by checking the version number matches or exceeds the fixed releases
Caveat Review release notes for your version branch to check for any configuration or behavior changes; minor version upgrades typically have low risk

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
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,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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