dbcve.org
ImagemagickApplication

CVE-2026-25989

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 can cause a denial of service. An off-by-one boundary check (`>` instead of `>=`) that allows bypass the guard and reach an undefined `(size_t)` cast. 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 an off-by-one error in SVG file parsing where a boundary check uses `>` instead of `>=`, allowing crafted SVG files to bypass a guard and trigger an undefined (size_t) cast resulting in denial of service.

MitigationUpgrade ImageMagick to version 7.1.2-15 or 6.9.13-40 or later to apply the patch that corrects the boundary check logic in SVG 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-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. Determine installed ImageMagick version
    Run `magick --version` or `identify --version` to obtain the version number. If using the delegate library, check `convert --version`. Compare the version to the affected ranges: < 6.9.13-40 or >= 7.0.0-0 and < 7.1.2-15.
    Affected if The installed version falls within < 6.9.13-40 or >= 7.0.0-0, < 7.1.2-15.
  2. Confirm SVG delegate support is present
    Run `magick -list configure | grep DELEGATES` or check for SVG support in the ImageMagick configuration. The vulnerability exists in SVG parsing, so SVG support must be compiled in or available.
    Affected if SVG delegate support is enabled in the ImageMagick build.
  3. Verify SVG processing capability is accessible
    Test if ImageMagick can process SVG files by running `magick input.svg output.png` with a test SVG file. Check if the SVG coder is loaded by running `magick -list coder`.
    Affected if SVG files can be processed by the ImageMagick installation.

The environment is affected if ImageMagick is installed with a version prior to 6.9.13-40 or between 7.0.0-0 and 7.1.2-15, AND SVG file processing capability is enabled and accessible.

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 to apply the patch that corrects the boundary check logic in SVG processing.

Recommended fix High confidence

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

  1. 1. Identify your current ImageMagick version using 'convert --version' or 'magick --version'
  2. 2. If using ImageMagick 6.x branch (< 6.9.13-40), upgrade to version 6.9.13-40 or later
  3. 3. If using ImageMagick 7.x branch (>= 7.0.0-0, < 7.1.2-15), upgrade to version 7.1.2-15 or later
  4. 4. On Debian/Ubuntu: run 'sudo apt-get update && sudo apt-get install imagemagick' or manually download from https://imagemagick.org/archive/
  5. 5. On RHEL/CentOS: run 'sudo yum update ImageMagick' or 'sudo dnf update ImageMagick'
  6. 6. On macOS with Homebrew: run 'brew upgrade imagemagick'
  7. 7. Verify the upgrade was successful by checking the version: 'convert --version'
  8. 8. Test with the original crafted SVG file to confirm the vulnerability is patched
Caveat Minimal risk - point releases typically contain only bug fixes; however, test critical image processing 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
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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