dbcve.org
ImagemagickApplication

CVE-2026-56374

HIGH · 7.1 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to 7.1.2-19 or later.
See remediation →
74/100
Remediation priority · Elevated
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-19 contains a heap buffer overflow vulnerability in the FTXT encoder due to missing boundary checks when parsing ftxt:format. Remote attackers can trigger an out of bounds read by crafting malicious FTXT image files to cause denial of service or information disclosure.

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-19 contain a heap buffer overflow vulnerability in the FTXT encoder. The vulnerability stems from missing boundary checks when parsing the ftxt:format attribute, allowing remote attackers to trigger an out-of-bounds read by crafting malicious FTXT image files, leading to denial of service or information disclosure.

MitigationUpgrade ImageMagick to version 7.1.2-19 or later. If upgrading is not immediately feasible, consider disabling FTXT format support or implementing input validation filters for image files before processing.

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:< 7.1.2-19

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
High
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/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 retrieve the installed version number
    Affected if The version number is lower than 7.1.2-19
  2. Verify FTXT format support is present
    Run `identify -list format` and look for FTXT in the list of supported formats, or check for ftxt.c in the coders directory
    Affected if FTXT appears in the list of supported formats and the ImageMagick version is below 7.1.2-19
  3. Check for active FTXT file handling
    Review image processing workflows or logs to see if FTXT files are accepted as input, or test with `identify -list format | grep -i ftxt`
    Affected if FTXT format is enabled and the version is below 7.1.2-19
  4. Inspect coder configuration
    Check the coders.xml or policy.xml configuration file for FTXT-related settings, typically found in /etc/ImageMagick-6/ or /etc/ImageMagick-7/
    Affected if FTXT coder is not explicitly disabled and version is below 7.1.2-19

You are affected if ImageMagick version is below 7.1.2-19 AND FTXT format support is enabled in your environment.

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 7.1.2-19 or later
Fixed in 7.1.2-19
Interim mitigation

Upgrade ImageMagick to version 7.1.2-19 or later. If upgrading is not immediately feasible, consider disabling FTXT format support or implementing input validation filters for image files before processing.

Recommended fix High confidence

ImageMagick 7.1.2-19 or later

  1. Check current ImageMagick version using 'convert -version' or 'identify -version'
  2. Backup any custom ImageMagick configuration files in /etc/ImageMagick* or /usr/local/etc/ImageMagick*
  3. Update package repository metadata: 'apt-get update' (Debian/Ubuntu) or 'yum check-update' (RHEL/CentOS)
  4. Upgrade ImageMagick: 'apt-get install imagemagick' (Debian/Ubuntu) or 'yum update imagemagick' (RHEL/CentOS)
  5. Verify installation of version 7.1.2-19 or later using 'convert -version'
  6. Test ImageMagick functionality with your application workflows
Caveat Minor version upgrades typically maintain backward compatibility; however, custom coders/loaders or policy.xml restrictions may need review

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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