dbcve.org
ImagemagickApplication

CVE-2026-26983

MEDIUM · 5.3 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 →
62/100
Remediation priority · Elevated
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, the MSL interpreter crashes when processing a invalid `<map>` element that causes it to use an image after it has been freed. 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 contains a use-after-free vulnerability in its MSL (Magick Scripting Language) interpreter. When processing an invalid `<map>` element, the interpreter frees an image but then attempts to access it afterward, causing a crash. This is a memory safety issue that can be triggered by maliciously crafted MSL script input.

MitigationUpgrade ImageMagick to version 7.1.2-15 or 6.9.13-40 or later to obtain the patch. If MSL scripts are processed from untrusted sources, implement input validation and consider sandboxing.

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 see the installed ImageMagick version and confirm it is present on the system
    Affected if No output means ImageMagick is not installed and is not affected
  2. Compare installed version to affected ranges
    Examine the version number from the previous step. Check if it is below 6.9.13-40, or between 7.0.0-0 and 7.1.2-15 (inclusive of the start, exclusive of 7.1.2-15)
    Affected if The installed version falls within < 6.9.13-40 or >= 7.0.0-0 AND < 7.1.2-15
  3. Confirm MSL interpreter support is enabled
    Run 'convert -list configure' or 'magick -list configure' and look for DELEGATES or a reference to MSL. Alternatively, check if the 'msl:' prefix is recognized by running 'identify msl:none' which may show whether MSL is compiled in
    Affected if MSL support is present in the build configuration and the version is vulnerable per step 2
  4. Check for MSL script processing in your environment
    Search for .msl files in your application directories, review application logs for 'msl:' URL prefixes or references to Magick Scripting Language, and identify any user-uploaded or externally sourced MSL scripts being processed
    Affected if Your system processes MSL scripts from any source, particularly untrusted or user-supplied MSL input containing <map> elements

You are affected if ImageMagick is installed with a vulnerable version (< 6.9.13-40 or >= 7.0.0-0 and < 7.1.2-15) AND your environment processes MSL scripts that could contain specially crafted <map> elements.

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 obtain the patch. If MSL scripts are processed from untrusted sources, implement input validation and consider sandboxing.

Recommended fix High confidence

6.9.13-40 for 6.x branch or 7.1.2-15 for 7.x branch

  1. Identify the currently installed ImageMagick version using `convert -version` or `magick -version`
  2. Determine which branch (6.x or 7.x) is currently in use
  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. Verify the upgrade was successful by checking the new version
  6. Test that ImageMagick functionality remains intact after the upgrade
Caveat Patch releases typically have minimal breaking changes; however, test ImageMagick workflows after upgrade to ensure compatibility

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
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,520
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,432.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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