dbcve.org
ImagemagickApplication

CVE-2026-47166

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-23 or later.
See remediation →
59/100
Remediation priority · Elevated
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-23, an attacker who can connect to a magick -distribute-cache service can cause a heap buffer over-read in the server process. This issue has been patched in versions 6.9.13-48 and 7.1.2-23.

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 versions prior to 6.9.13-48 and 7.1.2-23 contain a heap buffer over-read vulnerability in the magick-distribute-cache service. An attacker who can establish a network connection to this service can trigger the over-read in the server process.

MitigationUpdate ImageMagick to version 6.9.13-48 or 7.1.2-23 or later. If the magick-distribute-cache service is not required, consider disabling it to reduce attack surface.

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

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

CVSS:3.1/AV:L/AC:H/PR:H/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 if magick-distribute-cache service is running
    On Linux/Unix: ps aux | grep -i 'magick-distribute-cache' or systemctl status magick-distribute-cache. On Windows: check services list for 'ImageMagick Distributed Cache' or check running processes.
    Affected if Service is not running - vulnerability does not apply
  2. Check installed ImageMagick version
    Run 'convert -version' or 'magick -version' from command line to display the installed version string.
    Affected if Version cannot be determined - cannot assess exposure
  3. Compare version to affected ranges for ImageMagick 6.x
    If version starts with 6.9.x, check if it is less than 6.9.13-48. For example, 6.9.13-47 is affected, 6.9.13-48 and later are not.
    Affected if Version is 6.9.x and less than 6.9.13-48, AND magick-distribute-cache is running
  4. Compare version to affected ranges for ImageMagick 7.x
    If version starts with 7.x, check if it is less than 7.1.2-23. For example, 7.1.2-22 is affected, 7.1.2-23 and later are not.
    Affected if Version is 7.x and less than 7.1.2-23, AND magick-distribute-cache is running

You are affected if the magick-distribute-cache service is running AND your ImageMagick version is below 6.9.13-48 (for 6.x) or below 7.1.2-23 (for 7.x).

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-23 or later
Fixed in 6.9.13-487.1.2-23
Interim mitigation

Update ImageMagick to version 6.9.13-48 or 7.1.2-23 or later. If the magick-distribute-cache service is not required, consider disabling it to reduce attack surface.

Recommended fix High confidence

ImageMagick 6.9.13-48+ (6.x branch) or 7.1.2-23+ (7.x branch)

  1. Check the current ImageMagick version installed (e.g., 'convert -version' or 'magick -version')
  2. Identify whether you are running the 6.x or 7.x branch
  3. For 6.x branch: Upgrade to version 6.9.13-48 or later
  4. For 7.x branch: Upgrade to version 7.1.2-23 or later
  5. Use your system's package manager to apply the upgrade (e.g., apt update && apt upgrade imagemagick, yum update ImageMagick, or brew upgrade imagemagick)
  6. Verify the installed version matches the required patch level
  7. If using the magick-distribute-cache service, restart the service after upgrade

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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