dbcve.org
ImagemagickApplication

CVE-2026-25968

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 stack buffer overflow occurs when processing the an attribute in msl.c. A long value overflows a fixed-size stack buffer, leading to memory corruption. 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

Stack buffer overflow vulnerability in ImageMagick's MSL (Magick Scripting Language) parser (msl.c) when processing a specific attribute. A long/oversized value overflows a fixed-size stack buffer, leading to memory corruption and potential remote code execution.

MitigationUpgrade ImageMagick to version 7.1.2-15 or 6.9.13-40 or later to patch the stack buffer overflow 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
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 ImageMagick version
    Run 'convert --version' or 'magick --version' to display the installed ImageMagick version number
    Affected if The version shown is less than 6.9.13-40, OR is 7.0.0.0 through 7.1.2-14 (inclusive)
  2. Verify MSL coder availability
    Run 'convert -list configure | findstr /i msl' or check the coders directory for msl-related files
    Affected if MSL support is present in the ImageMagick installation and the version is in the affected range from step 1
  3. Check for MSL script processing
    Search for .msl files in your environment or look for applications that invoke ImageMagick with MSL scripts (e.g., 'convert input.msl output')
    Affected if MSL scripts are being processed and the version is in the affected range from step 1

You are affected if your installed ImageMagick version falls below 6.9.13-40 or between 7.0.0-0 and 7.1.2-14 AND you have MSL script processing capability enabled in your environment.

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 stack buffer overflow vulnerability.

Recommended fix High confidence

ImageMagick 7.1.2-15 or later for v7.x; ImageMagick 6.9.13-40 or later for v6.x

  1. Identify your current ImageMagick version using 'convert -version' or 'magick --version'
  2. For Debian/Ubuntu systems: Run 'sudo apt update' followed by 'sudo apt install imagemagick'
  3. For RHEL/CentOS/Fedora systems: Run 'sudo yum update imagemagick' or 'sudo dnf update imagemagick'
  4. For Alpine systems: Run 'sudo apk update' followed by 'sudo apk upgrade imagemagick'
  5. If installing from source, download ImageMagick 7.1.2-15 or later (for v7) or 6.9.13-40 or later (for v6) from https://imagemagick.org/archive/
  6. After upgrade, restart any services using ImageMagick (e.g., web servers, image processing daemons)
  7. Verify the new version is installed by running 'convert -version' or 'magick --version'
Caveat Minor: Some legacy ImageMagick syntax or deprecated features may behave differently; 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
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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