dbcve.org
ImagemagickApplication

CVE-2026-42326

MEDIUM · 5.1 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 6.9.13-47 / 7.1.2-22 or later.
See remediation →
56/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-47 and 7.1.2-22, when writing an IPTC output file a malicious input file could cause an out of bounds read of a single byte. This issue has been patched in versions 6.9.13-47 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

ImageMagick contains an out-of-bounds read vulnerability when writing IPTC output files. A specially crafted malicious input file can trigger a single-byte out-of-bounds read, potentially leading to information disclosure or a denial-of-service condition. The vulnerability affects versions prior to 6.9.13-47 and 7.1.2-22.

MitigationUpgrade ImageMagick to version 6.9.13-47 or 7.1.2-22 or later. If immediate patching is not possible, avoid processing untrusted image files with ImageMagick, particularly those that may involve IPTC metadata 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-47>= 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/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. Verify ImageMagick is installed
    Run `convert --version` (for 6.x) or `magick --version` (for 7.x) to confirm ImageMagick is present and retrieve version information
    Affected if Command returns a version number, indicating ImageMagick is installed
  2. Identify installed version number
    Parse the output from the version command to obtain the exact version (e.g., 6.9.13-30 or 7.1.2-10)
    Affected if Version output shows a specific version number that can be compared against the affected ranges
  3. Confirm version is in vulnerable range
    Compare your installed version: for 6.x branch, check if < 6.9.13-47; for 7.x branch, check if >= 7.0.0-0 and < 7.1.2-22
    Affected if Installed version falls below 6.9.13-47 (6.x) or is between 7.0.0-0 and 7.1.2-21 inclusive (7.x)
  4. Determine if IPTC output is being generated
    Inspect your ImageMagick usage or application logs for IPTC-related operations, such as converting to IPTC format or using IPTC metadata handlers in your processing pipeline
    Affected if Your workflow processes files to produce IPTC output files using ImageMagick's metadata writing functionality

You are affected if your ImageMagick version is below 6.9.13-47 (6.x branch) or below 7.1.2-22 (7.x branch) AND you use ImageMagick to generate IPTC output files from input files.

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-47 / 7.1.2-22 or later
Fixed in 6.9.13-477.1.2-22
Interim mitigation

Upgrade ImageMagick to version 6.9.13-47 or 7.1.2-22 or later. If immediate patching is not possible, avoid processing untrusted image files with ImageMagick, particularly those that may involve IPTC metadata operations.

Recommended fix High confidence

6.9.13-47 (for ImageMagick 6.x) or 7.1.2-22 (for ImageMagick 7.x)

  1. Check your current ImageMagick version by running 'convert -version' or 'magick -version'
  2. For Debian/Ubuntu systems: run 'sudo apt-get update' then 'sudo apt-get install imagemagick' to upgrade to the latest available version
  3. For RHEL/CentOS/Fedora systems: run 'sudo yum update imagemagick' or 'sudo dnf update imagemagick'
  4. For macOS with Homebrew: run 'brew upgrade imagemagick'
  5. For source installations: download and compile ImageMagick 6.9.13-47 or 7.1.2-22 from source.imagemagick.org
  6. Verify the upgrade was successful by running 'convert -version' and confirming the version is 6.9.13-47 or higher, or 7.1.2-22 or higher

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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