dbcve.org
ImagemagickApplication

CVE-2026-28493

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 7.1.2-16 or later.
See remediation →
74/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-16, an integer overflow vulnerability exists in the SIXEL decoer. The vulnerability allows an attacker to perform an out of bounds via a specially crafted image. This vulnerability is fixed in 7.1.2-16.

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

ImageMagick contains an integer overflow vulnerability in its SIXEL decoder. By providing a specially crafted image file with specific dimensions or parameters, an attacker can trigger the overflow, leading to an out-of-bounds memory write. This vulnerability affects versions prior to 7.1.2-16 and was addressed by implementing proper bounds checking in the SIXEL decoder.

MitigationUpgrade ImageMagick to version 7.1.2-16 or later. Additionally, implement input validation to reject untrusted or specially crafted image files before processing, and consider sandboxing ImageMagick operations to limit the impact of potential exploitation.

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:< 7.1.2-16

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/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. Confirm ImageMagick is installed
    Run `convert --version` or `magick --version` to check if ImageMagick is present on the system
    Affected if No output or command not found indicates ImageMagick is not installed (not affected)
  2. Identify the installed ImageMagick version
    Run `convert --version` and examine the version string (e.g., 7.1.2-15, 7.1.1-10)
    Affected if Version is less than 7.1.2-16 (e.g., 7.1.2-15, 7.1.2-0, 7.1.1-x)
  3. Check if SIXEL decoder support is enabled
    Run `identify -list format | grep -i sixel` or check ImageMagick configuration files for SIXEL-related delegates or coders
    Affected if SIXEL format support is listed as available/enabled in the output

You are affected if ImageMagick is installed with a version lower than 7.1.2-16 AND the SIXEL decoder is enabled, as the vulnerability requires processing a specially crafted SIXEL image file to trigger the integer overflow.

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 7.1.2-16 or later
Fixed in 7.1.2-16
Interim mitigation

Upgrade ImageMagick to version 7.1.2-16 or later. Additionally, implement input validation to reject untrusted or specially crafted image files before processing, and consider sandboxing ImageMagick operations to limit the impact of potential exploitation.

Recommended fix High confidence

ImageMagick 7.1.2-16 or later

  1. 1. Identify your current ImageMagick version by running 'convert -version' or 'magick -version'
  2. 2. Check your system's package manager for available updates (apt, yum, dnf, brew, etc.)
  3. 3. Update ImageMagick to version 7.1.2-16 or later
  4. 4. On Debian/Ubuntu: sudo apt update && sudo apt install imagemagick
  5. 5. On RHEL/CentOS/Fedora: sudo dnf update ImageMagick
  6. 6. On macOS: brew upgrade imagemagick
  7. 7. Verify the upgrade was successful by running 'convert -version' and confirming the version is 7.1.2-16 or higher
  8. 8. Test that your image processing workflows still function correctly after the upgrade
Caveat Minor version upgrades within 7.1.x typically maintain backward compatibility; however, test critical image processing workflows after upgrading

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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