dbcve.org
ImagemagickApplication

CVE-2026-30931

HIGH · 7.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 7.1.2-16 or later.
See remediation →
80/100
Remediation priority · High
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, a heap-based buffer overflow in the UHDR encoder can happen due to truncation of a value and it would allow an out of bounds write. 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 · high confidence

A heap-based buffer overflow vulnerability exists in ImageMagick's UHDR (Ultra High Dynamic Range) encoder due to value truncation. This allows an attacker to trigger an out-of-bounds write by providing a specially crafted image, potentially leading to memory corruption and code execution.

MitigationUpgrade ImageMagick to version 7.1.2-16 or later to remediate this vulnerability. Audit all systems and applications that depend on ImageMagick for image processing and apply the update accordingly.

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

CVSS:3.1/AV:L/AC:L/PR:L/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. Confirm ImageMagick installation and version
    Run 'identify -version' or 'magick --version' to retrieve the installed ImageMagick version
    Affected if The installed version is less than 7.1.2-16
  2. Check for UHDR encoder support
    Run 'identify -list configure | grep -i uhdr' or check if UHDR-related libraries/modules exist in the ImageMagick installation directory
    Affected if UHDR encoding support is present in the installation
  3. Detect UHDR processing in active use
    Review application logs, image processing workflows, or config files for references to UHDR, HDR, or Ultra High Dynamic Range image encoding
    Affected if Any workflow actively processes UHDR-format images using ImageMagick
  4. Inspect ImageMagick policy or delegate configurations
    Check /etc/ImageMagick-6/policy.xml or similar policy files for any UHDR-related coder delegates or enabled modules
    Affected if UHDR coder/delegate is explicitly enabled in the configuration

You are affected if ImageMagick is installed with a version prior to 7.1.2-16 and UHDR encoding functionality is available or being used to process images.

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 to remediate this vulnerability. Audit all systems and applications that depend on ImageMagick for image processing and apply the update accordingly.

Recommended fix High confidence

ImageMagick 7.1.2-16

  1. 1. Check the current ImageMagick version by running: `convert -version` or `magick -version`
  2. 2. Upgrade ImageMagick to version 7.1.2-16 or later
  3. - For Linux/Unix systems using package managers: `sudo apt-get update && sudo apt-get install imagemagick` (Debian/Ubuntu) or `sudo yum update ImageMagick` (RHEL/CentOS)
  4. - For macOS using Homebrew: `brew upgrade imagemagick`
  5. - For Windows: Download and install from the official ImageMagick website or use a package manager like Chocolatey
  6. 3. Verify the upgrade was successful by running: `convert -version` or `magick -version` and confirming the version is 7.1.2-16 or higher
  7. 4. Test that ImageMagick functions correctly with your workflows
Caveat None known from this specific security fix; minor version upgrades are typically backward compatible

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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