dbcve.org
ImagemagickApplication

CVE-2026-56366

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-10
Fix available
A fix is available. Upgrade to 6.9.13-43 / 7.1.2-18 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges 6 weeks old

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 before 7.1.2-18 contains a memory leak vulnerability in the META reader when processing APP1JPEG input paths. Attackers can trigger this memory leak by providing specially crafted APP1JPEG image files, causing denial of service through resource exhaustion.

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 before 7.1.2-18 contain a memory leak vulnerability in the META reader component when processing APP1JPEG input paths. Attackers can exploit this by providing specially crafted APP1JPEG image files, causing memory to be allocated but not released. This leads to resource exhaustion and denial of service.

MitigationUpgrade ImageMagick to version 7.1.2-18 or later. Additionally, implement input validation and file size limits for uploaded images to reduce exposure to maliciously crafted files.

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-43>= 7.0.0-0, < 7.1.2-18

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

CVSS:3.1/AV:N/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' or 'magick -version' to display the installed ImageMagick version number
    Affected if The version displayed is less than 6.9.13-43, or is 7.0.0-0 through 7.1.2-17 (inclusive)
  2. Confirm META coder availability
    Run 'identify -list configure | grep -i meta' or check the coders directory for the META coder module
    Affected if The META coder is present and loadable in the ImageMagick installation
  3. Test APP1JPEG processing capability
    Use 'identify -list coder' or 'magick identify -list coder' to verify the JPEG coder supports APP1 metadata handling
    Affected if JPEG support is enabled and APP1 metadata parsing is available in the environment
  4. Identify processes handling image uploads
    Audit application code or image processing pipelines that use ImageMagick to process JPEG files, looking for calls that trigger META or metadata reading
    Affected if The environment processes JPEG images through ImageMagick's META reader component, particularly where APP1 metadata is extracted or parsed

You are affected if your installed ImageMagick version falls within the vulnerable ranges AND your environment processes JPEG images using the META reader component to handle APP1 metadata.

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-43 / 7.1.2-18 or later
Fixed in 6.9.13-437.1.2-18
Interim mitigation

Upgrade ImageMagick to version 7.1.2-18 or later. Additionally, implement input validation and file size limits for uploaded images to reduce exposure to maliciously crafted files.

Recommended fix Moderate confidence

ImageMagick 6.9.13-43+ or 7.1.2-18+ (depending on your major version)

  1. 1. Identify the currently installed ImageMagick version using 'convert --version' or 'magick --version'
  2. 2. For ImageMagick 6.x users: upgrade to version 6.9.13-43 or later
  3. 3. For ImageMagick 7.x users: upgrade to version 7.1.2-18 or later
  4. 4. Verify the upgrade was successful by checking the version again
  5. 5. Test ImageMagick functionality with your image processing workflows

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 / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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