dbcve.org
ImagemagickApplication

CVE-2026-26283

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 `continue` statement in the JPEG extent binary search loop in the jpeg encoder causes an infinite loop when writing persistently fails. An attacker can trigger a 100% CPU consumption and process hang (Denial of Service) with a crafted image. 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

A `continue` statement in the JPEG extent binary search loop within ImageMagick's JPEG encoder causes an infinite loop when writing operations persistently fail. An attacker can trigger 100% CPU consumption and process hang by providing a crafted image that causes the encoder to enter this infinite loop condition.

MitigationUpdate ImageMagick to version 7.1.2-15 or later (or 6.9.13-40 or later for the 6.x branch) to obtain the patched version that fixes the infinite loop in the JPEG encoder.

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. Check installed ImageMagick version
    Run `convert --version` (for ImageMagick 6.x) or `magick --version` (for ImageMagick 7.x) to determine the exact version number installed in your environment
    Affected if The version shown is below 6.9.13-40 for the 6.x branch, or below 7.1.2-15 but at or above 7.0.0-0 for the 7.x branch
  2. Confirm JPEG processing is in use
    Identify whether your ImageMagick workflows involve encoding or writing JPEG images. Check your scripts, command-line invocations, or application code that calls ImageMagick for JPEG output operations
    Affected if Your environment processes JPEG images using ImageMagick's write operations

You are affected if your installed ImageMagick version falls within the vulnerable ranges (< 6.9.13-40 or >= 7.0.0-0 but < 7.1.2-15) AND you process JPEG images that could trigger the encoder's binary search loop under failure conditions.

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

Update ImageMagick to version 7.1.2-15 or later (or 6.9.13-40 or later for the 6.x branch) to obtain the patched version that fixes the infinite loop in the JPEG encoder.

Recommended fix High confidence

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

  1. 1. Identify the currently installed ImageMagick version using 'convert --version' or 'magick --version'
  2. 2. If using ImageMagick 6.x branch (versions < 6.9.13-40), upgrade to version 6.9.13-40 or later using your package manager or source compilation
  3. 3. If using ImageMagick 7.x branch (versions >= 7.0.0-0 and < 7.1.2-15), upgrade to version 7.1.2-15 or later using your package manager or source compilation
  4. 4. Verify the upgrade was successful by checking the new version matches or exceeds the fixed versions
  5. 5. Test image processing workflows to ensure functionality is maintained
Caveat Minor version upgrades within the same branch typically have no breaking changes; however, if upgrading from 6.x to 7.x, review the migration guide as API differences exist

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 / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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