dbcve.org
ImagemagickApplication

CVE-2026-46521

MEDIUM · 5.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 →
58/100
Remediation priority · Elevated
No privileges

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, when using LZMA compression in the MIFF encoder an out of bounds write can occur due to a missing check. 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 · moderate confidence

ImageMagick contains an out-of-bounds write vulnerability in the MIFF image encoder when processing LZMA-compressed image data. The issue stems from a missing bounds check that allows memory corruption during decompression, potentially leading to denial of service or arbitrary code execution.

MitigationUpgrade ImageMagick to version 6.9.13-48 or 7.1.2-23 or later. Until patched, avoid processing untrusted MIFF files with LZMA compression or disable LZMA support in ImageMagick.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Check installed ImageMagick version
    Run `identify -version` (ImageMagick 7) or `convert -version` (ImageMagick 6) to see the exact version number
    Affected if Version is below 6.9.13-48, or is 7.x and below 7.1.2-23
  2. Verify MIFF format support is present
    Run `identify -list format | grep -i miff` to confirm MIFF format is available in the build
    Affected if MIFF format appears in the list of supported formats (enabled by default in most builds)
  3. Confirm LZMA compression delegate is available
    Run `identify -list configure | grep -i lzma` or check for liblzma presence in the ImageMagick configuration
    Affected if LZMA support is present in the ImageMagick delegate configuration

The environment is affected if ImageMagick version is below the safe thresholds AND both MIFF format and LZMA compression support are enabled in the ImageMagick build.

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 6.9.13-48 or 7.1.2-23 or later. Until patched, avoid processing untrusted MIFF files with LZMA compression or disable LZMA support in ImageMagick.

Recommended fix High confidence

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

  1. Check current ImageMagick version using 'convert -version' or 'magick --version'
  2. If running ImageMagick 6.x (6.9.x): Upgrade to version 6.9.13-48 or later
  3. If running ImageMagick 7.x (7.0.x or 7.1.x): Upgrade to version 7.1.2-23 or later
  4. On Debian/Ubuntu: 'sudo apt-get update && sudo apt-get install imagemagick'
  5. On RHEL/CentOS/Fedora: 'sudo yum update ImageMagick' or 'sudo dnf update ImageMagick'
  6. On macOS with Homebrew: 'brew upgrade imagemagick'
  7. Verify the upgrade was successful by running 'convert -version' and confirming the installed version
Caveat Most users should not experience breaking changes; this is a security patch for an out-of-bounds write bug in the MIFF encoder's LZMA compression

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
  • Testing4.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,540
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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