dbcve.org
ImagemagickApplication

CVE-2026-25986

CRITICAL · 9.8 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 overflow write vulnerability exists in ReadYUVImage() (coders/yuv.c) when processing malicious YUV 4:2:2 (NoInterlace) images. The pixel-pair loop writes one pixel beyond the allocated row buffer. 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

Heap buffer overflow write vulnerability in ImageMagick's ReadYUVImage() function (coders/yuv.c). When processing malicious YUV 4:2:2 images with NoInterlace, the pixel-pair loop writes one pixel beyond the allocated row buffer, potentially allowing heap corruption and arbitrary code execution.

MitigationUpgrade ImageMagick to version 7.1.2-15/6.9.13-40 or later. If immediate upgrade is not feasible, restrict or disable YUV image processing in ImageMagick configurations.

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 'convert -version' to display the installed version number
    Affected if The version displayed is less than 6.9.13-40, or is 7.0.0.0 through 7.1.2-14 (inclusive)
  2. Verify YUV coder is available
    Run 'magick -list configure | grep -i yuv' or check for 'yuv' in 'magick -list coders' output
    Affected if The YUV coder appears in the list of available coders, meaning ImageMagick can process YUV images
  3. Identify YUV image files in your environment
    Use 'file' command or 'magick identify' on image files to detect YUV format (look for YUV, YCbCr, or YUV 4:2:2 in metadata)
    Affected if You have image files that are being processed as YUV 4:2:2 format with NoInterlace setting
  4. Check for NoInterlace setting in ImageMagick policies or defaults
    Review /etc/ImageMagick-6/policy.xml or /etc/ImageMagick-7/policy.xml for interlace-related settings; also check 'magick -list configure' for default interlace mode
    Affected if The environment defaults to NoInterlace or allows YUV images to be processed without explicit interlace configuration that would prevent the vulnerable code path

You are affected if your ImageMagick version falls within the vulnerable ranges AND YUV image processing is enabled and YUV 4:2:2 images with NoInterlace are being processed.

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. If immediate upgrade is not feasible, restrict or disable YUV image processing in ImageMagick configurations.

Recommended fix High confidence

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

  1. Check your current ImageMagick version using 'convert -version' or 'magick -version'
  2. If using ImageMagick 6.x series, upgrade to version 6.9.13-40 or later (e.g., 'apt-get update && apt-get install imagemagick' on Debian/Ubuntu, or 'yum update ImageMagick' on RHEL/CentOS)
  3. If using ImageMagick 7.x series, upgrade to version 7.1.2-15 or later
  4. After upgrade, verify the installed version matches or exceeds the fixed release
  5. Test that critical image processing workflows still function correctly after the upgrade
Caveat Standard security patch upgrade; minor version updates typically preserve backward compatibility but test critical image processing workflows

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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