dbcve.org
ImagemagickApplication

CVE-2026-26066

HIGH · 7.5 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 →
84/100
Remediation priority · High
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 profile contain invalid IPTC data may cause an infinite loop when writing it with `IPTCTEXT`. 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 denial-of-service vulnerability where a crafted image profile with invalid IPTC (International Press Telecommunications Council) metadata triggers an infinite loop during write operations using the IPTCTEXT parameter. An attacker can exploit this by providing a specially crafted image file, causing the application to hang and become unresponsive.

MitigationUpgrade ImageMagick to version 7.1.2-15/6.9.13-40 or later. If immediate upgrading is not feasible, implement input validation to reject or sanitize image files with untrusted IPTC metadata before processing.

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
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Identify installed ImageMagick version
    Run 'convert -version' (for ImageMagick 6) or 'magick -version' (for ImageMagick 7) to display the 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
  2. Confirm ImageMagick binary in use
    Run 'which convert' or 'which magick' to determine which binary is available on the system
    Affected if The binary resolves to an affected ImageMagick installation as per version check above
  3. Identify image processing workflows using write operations
    Review application code or scripts that invoke ImageMagick for write operations (e.g., convert input.jpg output.jpg, magick input.png output.png) especially on untrusted image files
    Affected if The workflow performs write operations on image files that may contain IPTC metadata from untrusted sources
  4. Check for IPTC metadata handling in processing pipeline
    Use 'identify -verbose imagefile' to inspect whether IPTC metadata (IPTC tags) is present in images processed by the system
    Affected if The system processes images that contain IPTC metadata, particularly from untrusted or user-supplied sources
  5. Verify IPTCTEXT parameter usage
    Search application logs, scripts, or code for use of 'IPTCTEXT' parameter or IPTC-related profile writing operations
    Affected if The environment uses IPTCTEXT parameter or writes IPTC profiles during image processing

The environment is affected if ImageMagick version is below 6.9.13-40 (6.x) or between 7.0.0-0 and 7.1.2-14 (7.x), AND the system processes or writes image files containing IPTC metadata from untrusted sources.

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 upgrading is not feasible, implement input validation to reject or sanitize image files with untrusted IPTC metadata before processing.

Recommended fix High confidence

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

  1. Check current ImageMagick version using `convert -version` or `magick -version`
  2. For ImageMagick 6.x line: upgrade to version 6.9.13-40 or later
  3. For ImageMagick 7.x line: upgrade to version 7.1.2-15 or later
  4. Verify the new version is installed: `convert -version` or `magick -version`
  5. Test that ImageMagick processes IPTC data without hanging

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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