dbcve.org
ImagemagickApplication

CVE-2026-30883

HIGH · 7.8 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 →
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 and 6.9.13-41, an extremely large image profile could result in a heap overflow when encoding a PNG image. 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 suffers from a heap overflow vulnerability when encoding PNG images that contain extremely large image profiles. The overflow occurs due to insufficient bounds checking during PNG encoding, allowing memory corruption that could potentially be exploited for code execution.

MitigationUpgrade ImageMagick to version 7.1.2-16 or 6.9.13-41 or later. Until upgraded, avoid processing untrusted PNG images with unusually large metadata profiles.

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
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. Identify installed ImageMagick version
    Run 'convert -version' or 'magick -version' to retrieve the exact version number of your ImageMagick installation
    Affected if The version is less than 6.9.13-41 for the 6.x branch, or between 7.0.0-0 and 7.1.2-16 (exclusive) for the 7.x branch
  2. Verify PNG encoder is available
    Run 'convert -list configure | grep DELEGATES' or 'magick -list configure' to confirm PNG support is compiled in
    Affected if PNG delegate support is present and the version falls within the affected ranges above
  3. Check for PNG processing with large profiles
    Review application logs, web server logs, or ImageMagick policy configurations for recent PNG encoding operations involving files with iTXt, tEXt, or zTXt chunks larger than typical (over 1MB)
    Affected if PNG images with unusually large metadata profiles have been processed and the ImageMagick version is affected
  4. Look for crash or memory corruption indicators
    Check system logs, application crash dumps, or ImageMagick warning/error logs for segmentation faults, heap errors, or memory allocation failures when PNG files were encoded
    Affected if Memory corruption, heap overflow errors, or unexpected crashes occurred during PNG encoding and the version is affected

You are affected if ImageMagick version is below 6.9.13-41 (6.x branch) or between 7.0.0-0 and 7.1.2-16 (7.x branch), and PNG encoding with large image profiles has been performed.

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. Until upgraded, avoid processing untrusted PNG images with unusually large metadata profiles.

Recommended fix High confidence

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

  1. Identify your current ImageMagick version by running 'convert --version' or 'magick --version'
  2. Determine whether you are using ImageMagick 6.x or 7.x from the version output
  3. For ImageMagick 6.x users: upgrade to version 6.9.13-41 or later
  4. For ImageMagick 7.x users: upgrade to version 7.1.2-16 or later
  5. Use your system's package manager to perform the upgrade (e.g., apt-get update && apt-get install imagemagick, yum update imagemagick, or brew upgrade imagemagick)
  6. Verify the upgrade was successful by running 'convert --version' and confirming the version number meets the fixed release criteria
  7. Test critical image processing workflows, particularly PNG encoding operations, to ensure functionality is intact
Caveat Point releases are typically backward compatible; however, test your workflows after upgrading as minor behavior changes can occur

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-30883 — 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-30883 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