dbcve.org
ImagemagickApplication

CVE-2026-42050

MEDIUM · 5.5 CVSS v3.1 Published 2026-05-11
Fix available
A fix is available. Upgrade to 6.9.13-46 / 7.1.2-21 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 7.1.2-21 and 6.9.13-46, a malicious MIFF file could trigger an overflow when a user opens it in the display tool and right-clicks a tile to invoke the Load / Update menu item. This vulnerability is fixed in 7.1.2-21 and 6.9.13-46.

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 · moderate confidence

A buffer/integer overflow vulnerability exists in ImageMagick's display tool when processing malicious MIFF (Magick Image File Format) files. The overflow is triggered specifically when a user opens a specially crafted MIFF file in the display tool and right-clicks a tile to invoke the Load/Update menu item. This vulnerability affects versions prior to 7.1.2-21 and 6.9.13-46.

MitigationUpgrade ImageMagick to version 7.1.2-21 or later for the 7.x branch, or version 6.9.13-46 or later for the 6.x branch. Until upgraded, avoid opening untrusted MIFF files in the ImageMagick display tool.

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-46>= 7.0.0-0, < 7.1.2-21

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Check ImageMagick version
    Run 'convert -version' (for 6.x) or 'magick -version' (for 7.x) to determine the installed version number
    Affected if Version is less than 6.9.13-46 or is 7.0.0-0 through 7.1.2-20
  2. Verify display tool availability
    Run 'display -version' or 'magick display -version' to confirm the display utility is installed
    Affected if The display command is present in the environment
  3. Confirm MIFF format support
    Run 'identify -list format' and search for 'MIFF' in the output to check if MIFF format is enabled
    Affected if MIFF format appears in the list of supported formats (indicates potential exposure)
  4. Identify usage of display tool with MIFF files
    Review any scripts, workflows, or user activities that invoke the 'display' or 'magick display' command on MIFF files, especially where right-click menu interaction occurs
    Affected if Users or automated processes open MIFF files using the display tool and interact with tiles

You are affected if ImageMagick version is below 6.9.13-46 or between 7.0.0-0 and 7.1.2-20, the display tool is installed, and MIFF files can be opened with right-click tile interaction enabled.

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-46 / 7.1.2-21 or later
Fixed in 6.9.13-467.1.2-21
Interim mitigation

Upgrade ImageMagick to version 7.1.2-21 or later for the 7.x branch, or version 6.9.13-46 or later for the 6.x branch. Until upgraded, avoid opening untrusted MIFF files in the ImageMagick display tool.

Recommended fix High confidence

ImageMagick 7.1.2-21 (for 7.x branch) or 6.9.13-46 (for 6.x branch)

  1. 1. Identify the currently installed ImageMagick version using `convert --version` or `magick --version`
  2. 2. If using ImageMagick 7.x (version 7.0.0-0 through 7.1.2-20), upgrade to version 7.1.2-21 or later
  3. 3. If using ImageMagick 6.x (version below 6.9.13-46), upgrade to version 6.9.13-46 or later
  4. 4. Verify the upgrade was successful by running `convert --version` and confirming the new version number
  5. 5. Test that MIFF file processing works correctly with the updated version

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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