dbcve.org
ImagemagickApplication

CVE-2026-56372

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-11
Fix available
A fix is available. Upgrade to 7.1.2-19 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 6 weeks old

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 before 7.1.2-19 contains a heap buffer overflow vulnerability in the magnify operation that allows attackers to read out of bounds memory. An unrecognized magnify:method value triggers an out of bounds read, potentially exposing sensitive information or causing denial of service.

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 before version 7.1.2-19 contains a heap buffer overflow vulnerability in the magnify operation where an unrecognized magnify:method value triggers an out of bounds memory read, potentially exposing sensitive information or causing denial of service.

MitigationUpgrade ImageMagick to version 7.1.2-19 or later to patch the vulnerability. If immediate upgrade is not feasible, consider disabling or restricting the magnify operation in policy configurations.

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-19

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
High
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Determine installed ImageMagick version
    Run 'convert --version' or 'magick --version' to retrieve the version number
    Affected if The installed version is before 7.1.2-19 (e.g., 7.1.2-18, 7.1.1-X, 6.X.X)
  2. Identify use of the magnify operation
    Search image processing scripts, configs, or application code for calls to the magnify operation or setting of 'magnify:method' parameter
    Affected if The environment processes images using ImageMagick's magnify feature with a user-controlled magnify:method value
  3. Check if ImageMagick processes untrusted input
    Review how ImageMagick is invoked - whether it processes images from untrusted sources (user uploads, external APIs, network sources) without prior validation
    Affected if Untrusted or attacker-controlled images can be processed through ImageMagick
  4. Inspect image processing pipelines for magnify settings
    Examine any ImageMagick policy files, delegate configurations, or custom coders that handle the magnify operation or parse image attributes
    Affected if Magnify-related processing is enabled and processes potentially untrusted image files

You are affected if ImageMagick version is below 7.1.2-19 AND your environment uses the magnify operation to process images with controllable magnify:method values.

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

Upgrade ImageMagick to version 7.1.2-19 or later to patch the vulnerability. If immediate upgrade is not feasible, consider disabling or restricting the magnify operation in policy configurations.

Recommended fix Moderate confidence

7.1.2-19 or later (7.1.x stable release)

  1. Check current ImageMagick version by running `convert --version` or `magick --version`
  2. Update your system's package list: `sudo apt-get update` (Debian/Ubuntu) or `sudo yum check-update` (RHEL/CentOS)
  3. Upgrade ImageMagick: `sudo apt-get install imagemagick` (Debian/Ubuntu) or `sudo yum update ImageMagick` (RHEL/CentOS)
  4. Verify the upgrade was successful by running `convert --version` or `magick --version` and confirming the version is 7.1.2-19 or higher
  5. Test critical image processing workflows to ensure functionality is unaffected
Caveat Review release notes for 7.1.2-x series to check for behavior changes in image processing; some legacy policies or delegates may require updates

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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