dbcve.org
ImagemagickApplication

CVE-2026-25798

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 NULL pointer dereference in ClonePixelCacheRepository allows a remote attacker to crash any application linked against ImageMagick by supplying a crafted image file, resulting in denial of service. 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 NULL pointer dereference vulnerability in the ClonePixelCacheRepository function of ImageMagick allows remote attackers to crash any application linked against the library by supplying a crafted image file, resulting in denial of service.

MitigationUpgrade ImageMagick to version 7.1.2-15 or 6.9.13-40 or later to patch the NULL pointer dereference vulnerability.

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. Identify ImageMagick installation
    Run 'convert -version' or 'magick -version' to display the installed ImageMagick version and confirm the product name
    Affected if No output is returned, indicating ImageMagick is not installed or not accessible in PATH
  2. Extract the precise version number
    Parse the output from 'convert -version' to obtain the exact version string (e.g., 7.1.2-14 or 6.9.13-30)
    Affected if The version cannot be determined or the command fails
  3. Compare version against affected ranges
    Check if the installed version is either less than 6.9.13-40, or between 7.0.0-0 and 7.1.2-14 inclusive
    Affected if The installed version falls within < 6.9.13-40 or >= 7.0.0-0 and < 7.1.2-15
  4. Identify applications linked against ImageMagick
    For custom applications, use 'ldd <executable>' or check for ImageMagick library dependencies to confirm the application links against libMagick or libMagickCore
    Affected if The application is dynamically linked against ImageMagick libraries and processes external image input
  5. Determine if application processes untrusted images
    Review application configuration or code to verify whether it accepts image files from external or untrusted sources that could supply a crafted file
    Affected if The application accepts image input from users or external sources without validation

A user is affected if ImageMagick version is less than 6.9.13-40 or between 7.0.0-0 and 7.1.2-14, and an application linked against the library processes crafted image files from untrusted sources.

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 patch the NULL pointer dereference vulnerability.

Recommended fix High confidence

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

  1. Identify the currently installed ImageMagick version using 'convert --version' or 'magick --version'
  2. Determine which major version branch is in use (6.x or 7.x)
  3. For systems using ImageMagick 6.x: upgrade to version 6.9.13-40 or later
  4. For systems using ImageMagick 7.x: upgrade to version 7.1.2-15 or later
  5. Use package manager appropriate for the system (e.g., 'apt-get install imagemagick', 'yum update ImageMagick', or compile from source)
  6. Verify the installed version matches the target fixed version using 'convert --version'
  7. Restart any services or applications that use ImageMagick to ensure the new library is loaded
Caveat Review release notes for behavior changes between versions; test 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
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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