dbcve.org
ImagemagickApplication

CVE-2026-25967

HIGH · 7.5 CVSS v3.1 Published 2026-02-24
Fix available
A fix is available. Upgrade to 6.9.13-40 / 7.1.2-15 or later.
See remediation →
84/100
Remediation priority · High
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 is free and open-source software used for editing and manipulating digital images. Prior to version 7.1.2-15, a stack-based buffer overflow exists in the ImageMagick FTXT image reader. A crafted FTXT file can cause out-of-bounds writes on the stack, leading to a crash. Version 7.1.2-15 contains a patch.

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

A stack-based buffer overflow exists in ImageMagick's FTXT (formatted text) image reader prior to version 7.1.2-15. A specially crafted FTXT file with malformed data triggers out-of-bounds memory writes on the stack, leading to a crash (denial of service).

MitigationUpgrade ImageMagick to version 7.1.2-15 or later. As a defense-in-depth measure, configure ImageMagick to reject or sanitize untrusted FTXT files, or disable the FTXT coder if not required.

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
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Determine installed ImageMagick version
    Run `identify -version` or `magick -version` to obtain the exact version number
    Affected if The version is less than 6.9.13-40, or is 7.0.0-0 through 7.1.2-14 (i.e., < 7.1.2-15)
  2. Check if FTXT coder is available
    Run `identify -list configure | grep -i ftxt` or examine the coders directory for ftxt-related files (e.g., ftxt.c, FTXT.so)
    Affected if The FTXT coder is present and loaded by ImageMagick
  3. Verify FTXT support in ImageMagick policy
    Examine /etc/ImageMagick-6/policy.xml or /etc/ImageMagick/policy.xml for any <policy> entries that restrict or disable the FTXT coder (look for pattern="FTXT" or pattern="ftxt")
    Affected if No policy rule exists to block or restrict the FTXT coder, meaning it can process FTXT files
  4. Check if FTXT image processing is occurring
    Review ImageMagick logs or audit trails for recent attempts to read or process .ftxt files, or query any image processing pipelines that may accept FTXT input
    Affected if FTXT files are being processed by the ImageMagick installation

You are affected if your ImageMagick version falls within the vulnerable range AND the FTXT coder is enabled and capable of processing FTXT 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-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 or later. As a defense-in-depth measure, configure ImageMagick to reject or sanitize untrusted FTXT files, or disable the FTXT coder if not required.

Recommended fix High confidence

ImageMagick 7.1.2-15 (or 6.9.13-40 for 6.x branch)

  1. Check your current ImageMagick version using 'convert -version' or 'magick -version'
  2. For ImageMagick 7.x users: Upgrade to version 7.1.2-15 or later
  3. For ImageMagick 6.x users: Upgrade to version 6.9.13-40 or later
  4. On Debian/Ubuntu: Run 'apt update && apt install imagemagick' or specify version with 'apt install imagemagick=7.1.2-15'
  5. On RHEL/CentOS: Run 'yum update ImageMagick' or 'dnf update ImageMagick'
  6. On macOS with Homebrew: Run 'brew upgrade imagemagick'
  7. On Windows: Download and install the latest version from imagemagick.org
  8. Verify the new version is installed: 'convert -version'

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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