dbcve.org
ImagemagickApplication

CVE-2026-46522

HIGH · 7.5 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 →
84/100
Remediation priority · High
Remotely reachable 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 7.1.2.23 and 6.9.13-48, due to a missing check in the MIFF decoder, a crafted file could cause an infinite loop resulting in CPU exhaustion. Versions 7.1.2.23 and 6.9.13-48 fix the issue.

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 7.1.2.23 and 6.9.13-48 contain a missing validation check in the MIFF (Magick Image File Format) decoder. A specially crafted MIFF file can trigger an infinite loop, leading to complete CPU exhaustion and denial of service. The vulnerability is remotely exploitable through user-supplied image files.

MitigationUpgrade ImageMagick to version 7.1.2.23 or 6.9.13-48 or later. As a defensive measure, consider disabling MIFF format processing or implementing resource limits on image processing operations.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Identify installed ImageMagick version
    Run 'convert -version' for ImageMagick 6 or 'magick -version' for ImageMagick 7. On systems with package managers, also check 'dpkg -l imagemagick' or 'rpm -q imagemagick'.
    Affected if The version shown is less than 6.9.13-48, or is 7.0.0.0 through 7.1.2.22 (inclusive). Versions 6.9.13-48 and above, or 7.1.2.23 and above, are not affected.
  2. Verify MIFF format decoder is available
    Run 'identify -list format | grep -i miff' to confirm MIFF format support is compiled in. Alternatively, check if the MIFF coder exists in the module directory (often /usr/lib/ImageMagick-*/modules-Q16/coders/).
    Affected if MIFF format support is present and the version from step 1 is in the affected range.
  3. Check policy.xml for MIFF handling configuration
    Locate the policy.xml file (commonly in /etc/ImageMagick-6/ or /etc/ImageMagick-7/) and search for '<policy domain="coder" rights="none" pattern="MIFF"/>' or similar MIFF entries.
    Affected if There is no explicit MIFF restriction in the policy, meaning MIFF files can be processed by default.
  4. Test MIFF parsing behavior (optional confirmation)
    If a sample MIFF file is available, run 'identify <miff_file>' and observe CPU usage. An affected version may hang or show very high CPU usage during parsing.
    Affected if The command hangs or takes unusually long time, indicating infinite loop behavior during MIFF parsing.

You are affected if ImageMagick version is less than 6.9.13-48 or between 7.0.0.0 and 7.1.2.22, AND MIFF format support is enabled in your ImageMagick installation.

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

Upgrade ImageMagick to version 7.1.2.23 or 6.9.13-48 or later. As a defensive measure, consider disabling MIFF format processing or implementing resource limits on image processing operations.

Recommended fix High confidence

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

  1. 1. Identify the currently installed ImageMagick version using 'convert --version' or 'magick --version'
  2. 2. Determine which major version branch you are using (6.x or 7.x)
  3. 3. If using version 6.x (e.g., 6.9.x), upgrade to version 6.9.13-48 or later
  4. 4. If using version 7.x (e.g., 7.0.x or 7.1.x), upgrade to version 7.1.2-23 or later
  5. 5. On RHEL/RHEL-based systems, run 'dnf update ImageMagick' or 'yum update ImageMagick'
  6. 6. On Debian/Ubuntu systems, run 'apt-get update && apt-get install imagemagick'
  7. 7. On macOS with Homebrew, run 'brew upgrade imagemagick'
  8. 8. Verify the upgrade was successful by running 'convert --version' or 'magick --version' and confirming the version number meets the fixed release criteria
Caveat Review the ImageMagick release notes for your target version as there may be minor feature or behavior changes between releases

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