dbcve.org
ImagemagickApplication

CVE-2026-56370

HIGH · 7.8 CVSS v3.1 Published 2026-06-24
Fix available
A fix is available. Upgrade to 6.9.13-44 / 7.1.2-19 or later.
See remediation →
81/100
Remediation priority · High
No privileges 8 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 an out-of-bounds access vulnerability in ConnectedComponentsImage() when processing connected-components artifacts with invalid indices. Attackers can trigger access violations by specifying malformed connected-components definitions via CLI, causing denial of service or potential code execution.

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 7.1.2-19 contains an out-of-bounds access vulnerability in the ConnectedComponentsImage() function when processing connected-components artifacts with invalid indices. Attackers can trigger access violations by specifying malformed connected-components definitions via CLI, potentially leading to denial of service or code execution.

MitigationUpgrade to ImageMagick version 7.1.2-19 or later to patch the vulnerability. If immediate upgrading is not feasible, consider disabling or restricting the connected-components CLI operations or implementing input validation filters.

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-44>= 7.0.0-0, < 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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Check installed ImageMagick version
    Run 'identify -version' or 'magick --version' to obtain the installed version number
    Affected if The version is below 6.9.13-44, or is 7.0.0.0 through 7.1.2-18 (inclusive)
  2. Verify connected-components usage
    Search application logs, scripts, or documentation for usage of the 'connected-components' CLI operation or the ConnectedComponentsImage() API function
    Affected if The connected-components feature is actively used in any automated processing pipeline or called via CLI
  3. Assess CLI exposure
    Review whether the ImageMagick CLI is directly accessible to untrusted users or input sources (web uploads, API endpoints, user-supplied files)
    Affected if The CLI accepts input from untrusted or external sources without prior validation
  4. Check for artifact definition files
    Inspect any configuration files, scripts, or input data that define connected-components blob definitions or connected-component labeling parameters
    Affected if The environment processes custom or user-supplied connected-components definitions or artifacts

You are affected if your installed ImageMagick version falls within the vulnerable ranges AND the connected-components CLI operation is accessible or used in your environment.

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

Upgrade to ImageMagick version 7.1.2-19 or later to patch the vulnerability. If immediate upgrading is not feasible, consider disabling or restricting the connected-components CLI operations or implementing input validation filters.

Recommended fix High confidence

ImageMagick 7.1.2-19 (or 6.9.13-44 for 6.x branch)

  1. 1. Identify your current ImageMagick version by running 'convert --version' (for 6.x) or 'magick --version' (for 7.x)
  2. 2. If using ImageMagick 6.x, upgrade to version 6.9.13-44 or later using your system's package manager (e.g., apt-get install imagemagick, yum update imagemagick, or brew upgrade imagemagick)
  3. 3. If using ImageMagick 7.x, upgrade to version 7.1.2-19 or later using your system's package manager
  4. 4. Verify the upgrade was successful by running 'convert --version' or 'magick --version' and confirming the version number meets the fixed release criteria
  5. 5. Test any image processing workflows that use the connected-components functionality to ensure normal operation

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