dbcve.org
ImagemagickApplication

CVE-2026-25799

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 logic error in YUV sampling factor validation allows an invalid sampling factor to bypass checks and trigger a division-by-zero during image loading, resulting in a reliable 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 logic error in ImageMagick's YUV sampling factor validation allows an attacker to provide an invalid sampling factor that bypasses security checks. This triggers a division-by-zero error when loading a specially crafted image file, causing a reliable denial-of-service condition.

MitigationUpdate ImageMagick to version 7.1.2-15 or 6.9.13-40 or later to apply the patch that fixes the YUV sampling factor validation logic.

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 'identify -version' or 'magick -version' to check if ImageMagick is present on the system
    Affected if If the command fails or ImageMagick is not found, the system is not affected by this specific vulnerability
  2. Determine the installed ImageMagick version
    Examine the version output from the previous command. Look for a version number in the format 6.x.x or 7.x.x
    Affected if The version output will indicate whether further version comparison is needed
  3. Compare version against affected 6.x branch range
    If the version starts with 6.x, compare it to 6.9.13-40. The affected range is any version less than 6.9.13-40
    Affected if If the version is 6.9.13-x where x is less than 40, or any 6.x version below 6.9.13-40, the environment is affected
  4. Compare version against affected 7.x branch range
    If the version starts with 7.x, check if it is >= 7.0.0-0 AND < 7.1.2-15
    Affected if If the version is 7.0.0-0 through 7.1.2-14 (inclusive), the environment is affected
  5. Identify how ImageMagick is invoked in your environment
    Check for web applications, scripts, or services that call ImageMagick (magick, convert, identify) to process uploaded or external images
    Affected if If ImageMagick processes untrusted image files and the version is in the affected range, exploitation is possible

The environment is affected if ImageMagick is installed and the version falls below 6.9.13-40 in the 6.x branch, or is between 7.0.0-0 and 7.1.2-14 in the 7.x branch.

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

Update ImageMagick to version 7.1.2-15 or 6.9.13-40 or later to apply the patch that fixes the YUV sampling factor validation logic.

Recommended fix High confidence

Upgrade to ImageMagick 6.9.13-40 or later for the 6.x line, or 7.1.2-15 or later for the 7.x line

  1. Check current ImageMagick version: `convert --version` or `magick --version`
  2. For RHEL/CentOS/Fedora: Run `sudo dnf check-update` and `sudo dnf update ImageMagick` or `sudo yum update ImageMagick`
  3. For Debian/Ubuntu: Run `sudo apt-get update` and `sudo apt-get install imagemagick`
  4. For Alpine: Run `apk add --upgrade imagemagick`
  5. For macOS (Homebrew): Run `brew update` and `brew upgrade imagemagick`
  6. Verify the installed version matches or exceeds 6.9.13-40 (6.x line) or 7.1.2-15 (7.x line) using `convert --version`
  7. Test that ImageMagick functions correctly with your workflows
Caveat Minor: Some legacy MFEGN or PS2 coders may have deprecated behavior changes; review release notes if using specialized ImageMagick features

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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