dbcve.org
ImagemagickApplication

CVE-2026-45359

MEDIUM · 5.7 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 6.9.13-48 / 7.1.2-22 or later.
See remediation →
62/100
Remediation priority · Elevated
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 6.9.13-48 and 7.1.2-22, an invalid connected-components:keep-top value could result in a heap buffer over-read when performing the connected components operation. This issue has been patched in versions 6.9.13-48 and 7.1.2-22.

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 buffer over-read vulnerability exists in ImageMagick's connected components operation when an invalid connected-components:keep-top value is provided. This can be triggered by processing specially crafted input, potentially leading to information disclosure or denial of service.

MitigationUpgrade ImageMagick to version 6.9.13-48 or 7.1.2-22 or later to patch the vulnerability. Validate that image processing workflows function correctly after the upgrade.

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-48>= 7.0.0-0, < 7.1.2-22

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

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:L

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 `convert -version` (ImageMagick 6) or `magick -version` (ImageMagick 7) to identify the exact version number installed in your environment
    Affected if The version is below 6.9.13-48, or is 7.0.0-0 through 7.1.2-21 (excluding 7.1.2-22)
  2. Identify use of connected-components operation
    Search your application code, scripts, and ImageMagick policy configurations for invocations of the `connected-components` operator, particularly in any image processing pipelines or automated workflows
    Affected if The connected-components operation is actively used in your image processing workflows
  3. Inspect keep-top parameter usage
    If connected-components is used, examine any calls that include the `keep-top` parameter and verify whether user-supplied or unvalidated input could be passed to this parameter
    Affected if The keep-top parameter accepts input without validation or sanitization

You are affected if your ImageMagick version falls within the vulnerable range AND your system processes images using the connected-components operation with a keep-top parameter that can receive arbitrary input 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 6.9.13-48 / 7.1.2-22 or later
Fixed in 6.9.13-487.1.2-22
Interim mitigation

Upgrade ImageMagick to version 6.9.13-48 or 7.1.2-22 or later to patch the vulnerability. Validate that image processing workflows function correctly after the upgrade.

Recommended fix High confidence

Upgrade to ImageMagick 6.9.13-48 or later for the 6.x branch, or 7.1.2-22 or later for the 7.x branch

  1. Check current ImageMagick version with 'convert -version' or 'magick --version'
  2. For RHEL/CentOS/Fedora systems: run 'sudo dnf check-update' or 'sudo yum check-update' to see available updates
  3. For Debian/Ubuntu systems: run 'sudo apt update' followed by 'sudo apt list --upgradable' to see available updates
  4. Upgrade ImageMagick using system package manager: 'sudo dnf upgrade ImageMagick' (RHEL/Fedora) or 'sudo apt upgrade imagemagick' (Debian/Ubuntu)
  5. Verify the installed version is 6.9.13-48 or higher for the 6.x branch, or 7.1.2-22 or higher for the 7.x branch with 'convert -version'

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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