dbcve.org
ImagemagickApplication

CVE-2026-56371

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-23
Fix available
A fix is available. Upgrade to 6.9.13-40 / 7.1.2-15 or later.
See remediation →
62/100
Remediation priority · Elevated
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 before 7.1.2-15 and 6.9.13-40 contains a memory leak in coders/txt.c when processing TXT files with texture attributes: the texture object allocated via ReadImage is not released when GetTypeMetrics fails, leaking memory each time a crafted TXT file with a texture attribute is processed.

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 a memory leak in coders/txt.c where a texture object allocated via ReadImage is not properly released when GetTypeMetrics fails during TXT file processing with texture attributes. Each successful processing of a crafted TXT file with a texture attribute results in memory leakage, potentially leading to resource exhaustion.

MitigationUpgrade ImageMagick to version 7.1.2-15/6.9.13-40 or later to obtain the patch that adds proper texture object cleanup in the error path of GetTypeMetrics.

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-40>= 7.0.0-0, < 7.1.2-15

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Check installed ImageMagick version
    Run 'identify -version' or 'convert -version' to retrieve the version number
    Affected if Version is less than 6.9.13-40, or is 7.0.0-0 through 7.1.2-14 (inclusive)
  2. Verify TXT coder availability
    Run 'identify -list configure' and look for 'DELEGATES' or 'CODERS' containing 'txt', or check if ImageMagick can identify a TXT file type
    Affected if TXT coder support is enabled and ImageMagick version is in the affected range
  3. Confirm TXT file processing capability
    Attempt to process a basic TXT file with ImageMagick using 'convert input.txt output.png' or similar command
    Affected if ImageMagick can process TXT files and version is affected
  4. Check for texture attribute processing
    Inspect whether ImageMagick is configured to read or process TXT files that may contain texture attributes (search documentation for -texture or similar TXT texture options)
    Affected if TXT file processing with texture attributes is possible and version is in the affected range

A user is affected if their ImageMagick version falls within < 6.9.13-40 or >= 7.0.0-0 to < 7.1.2-15, and they process TXT files with texture attributes where GetTypeMetrics fails, causing memory accumulation.

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-40 / 7.1.2-15 or later
Fixed in 6.9.13-407.1.2-15
Interim mitigation

Upgrade ImageMagick to version 7.1.2-15/6.9.13-40 or later to obtain the patch that adds proper texture object cleanup in the error path of GetTypeMetrics.

Recommended fix High confidence

ImageMagick 6.9.13-40 or later; ImageMagick 7.1.2-15 or later

  1. 1. Identify the current ImageMagick version installed on the system using 'convert --version' or 'magick --version'
  2. 2. For ImageMagick 6.x users: Upgrade to version 6.9.13-40 or later
  3. 3. For ImageMagick 7.x users: Upgrade to version 7.1.2-15 or later
  4. 4. Verify the upgrade was successful by checking the version again
  5. 5. Test that ImageMagick processes TXT files normally to confirm functionality
Caveat Major version upgrades may have backward-incompatible changes; review release notes before upgrading

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