dbcve.org
ImagemagickApplication

CVE-2026-28693

HIGH · 8.1 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 6.9.13-41 / 7.1.2-16 or later.
See remediation →
90/100
Remediation priority · Urgent
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 and 6.9.13-41, an integer overflow in DIB coder can result in out of bounds read or write. This vulnerability is fixed in 7.1.2-16 and 6.9.13-41.

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-16 and 6.9.13-41 contain an integer overflow vulnerability in the DIB (Device Independent Bitmap) coder component. This flaw can allow an attacker to cause out-of-bounds memory reads or writes by supplying specially crafted DIB image files, potentially leading to information disclosure or code execution.

MitigationUpgrade ImageMagick to version 7.1.2-16 or 6.9.13-41 or later. If immediate upgrading is not feasible, consider disabling or restricting the DIB coder in ImageMagick's policy configuration to limit attack surface.

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-41>= 7.0.0-0, < 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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. Determine installed ImageMagick version
    Run `identify -version` or `magick --version` to get the exact version number
    Affected if The version displayed is less than 6.9.13-41 (for 6.x) OR is 7.0.0-0 through 7.1.2-15 (for 7.x)
  2. Verify DIB coder module availability
    Run `identify -list configure | grep DIB` or check if DIB is listed in `identify -list format` output
    Affected if DIB format support is present and loadable in the ImageMagick installation
  3. Confirm DIB/BMP processing is not disabled
    Check ImageMagick policy.xml (typically at /etc/ImageMagick-6/policy.xml or /etc/ImageMagick-7/policy.xml) for any <policy> entries that restrict DIB or BMP read/write operations
    Affected if No policy blocks or restrictions exist for DIB/BMP format processing
  4. Test DIB file processing capability
    Attempt to identify a sample DIB file using `identify sample.dib` - if it succeeds and displays image details, the DIB coder is active
    Affected if The command successfully processes the DIB file without errors, confirming the vulnerable coder is functional

You are affected if ImageMagick version is 6.x below 6.9.13-41 or 7.x below 7.1.2-16 AND the DIB coder is available and not blocked by policy.

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

Upgrade ImageMagick to version 7.1.2-16 or 6.9.13-41 or later. If immediate upgrading is not feasible, consider disabling or restricting the DIB coder in ImageMagick's policy configuration to limit attack surface.

Recommended fix High confidence

ImageMagick 6.9.13-41 (6.x branch) or 7.1.2-16 (7.x branch)

  1. Check current ImageMagick version using 'convert -version' or 'identify -version'
  2. For RHEL/CentOS/Fedora systems: run 'sudo dnf update ImageMagick' or 'sudo yum update ImageMagick'
  3. For Debian/Ubuntu systems: run 'sudo apt-get update' followed by 'sudo apt-get install imagemagick'
  4. For source installation: download and compile version 6.9.13-41 (6.x branch) or 7.1.2-16 (7.x branch) from https://imagemagick.org/archive/
  5. Verify the upgrade was successful by running 'convert -version' and confirming the version number matches or exceeds 6.9.13-41 or 7.1.2-16

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Imagemagick Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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