dbcve.org
ImagemagickApplication

CVE-2026-25983

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 crafted MSL script triggers a heap-use-after-free. The operation element handler replaces and frees the image while the parser continues reading from it, leading to a UAF in ReadBlobString during further parsing. 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 a heap-use-after-free vulnerability in the MSL (Magick Scripting Language) parser. When processing a crafted MSL script, the operation element handler prematurely replaces and frees the image object while the parser continues reading from it, causing a UAF condition in ReadBlobString during continued parsing. This memory safety flaw with CVSS 9.8 is remotely exploitable without authentication and could lead to arbitrary code execution.

MitigationUpgrade ImageMagick to version 7.1.2-15 or 6.9.13-40 or later. If upgrading is not immediately feasible, disable MSL script processing or restrict input sources to prevent untrusted MSL files from being processed.

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. Determine installed ImageMagick version
    Run 'convert --version' (ImageMagick 6) or 'magick --version' (ImageMagick 7) and note the version number
    Affected if The version is less than 6.9.13-40, or is 7.0.0.0 through 7.1.2-14 (versions prior to 7.1.2-15)
  2. Confirm the ImageMagick binary in use
    Run 'which convert' or 'which magick' to identify the binary path and ensure it matches the version check above
    Affected if The identified binary corresponds to a vulnerable version range
  3. Identify if MSL script processing is in use
    Search for .msl files in your environment, or check configuration files for MSL-related directives or script processing paths
    Affected if MSL scripts are present and processed by the ImageMagick installation
  4. Check for MSL handler registration
    Examine ImageMagick's coders.xml configuration or run 'magick -list configure' to see enabled coders and delegates; look for MSL delegate handler
    Affected if MSL scripting is enabled as a delegate handler in the ImageMagick configuration

You are affected if your installed ImageMagick version falls within the vulnerable ranges (below 6.9.13-40, or 7.0.0.0 through 7.1.2-14) AND MSL script processing is enabled or your environment handles .msl files.

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. If upgrading is not immediately feasible, disable MSL script processing or restrict input sources to prevent untrusted MSL files from being processed.

Recommended fix High confidence

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

  1. 1. Identify your current ImageMagick version using `convert --version` or `magick --version`
  2. 2. If using ImageMagick 6.x version < 6.9.13-40, upgrade to version 6.9.13-40 or later
  3. 3. If using ImageMagick 7.x version >= 7.0.0-0 and < 7.1.2-15, upgrade to version 7.1.2-15 or later
  4. 4. Verify the upgrade was successful by checking the new version with `convert --version`
  5. 5. Test your image processing workflows to ensure functionality is intact
Caveat Review release notes for your version branch to check for any deprecated features or behavioral changes in the upgrade path

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,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 $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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