dbcve.org
ImagemagickApplication

CVE-2026-61863

HIGH · 7.5 CVSS v3.1 Published 2026-07-15
Fix available
A fix is available. Upgrade to 6.9.13-51 / 7.1.2-26 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 5 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-26 (and 6.x before 6.9.13-51) contains a memory leak in the TIFF encoder that occurs when a temporary file cannot be created, resulting in a small memory leak.

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 prior to 7.1.2-26 (and 6.x prior to 6.9.13-51) have a memory leak vulnerability in the TIFF encoder. When the encoder attempts to create a temporary file and fails, it does not properly free allocated memory, resulting in a small memory leak that can accumulate over repeated failed operations.

MitigationUpgrade ImageMagick to version 7.1.2-26 or later (for 7.x), or version 6.9.13-51 or later (for 6.x). If upgrading is not immediately feasible, monitor TIFF processing operations and implement rate limiting on TIFF encoding requests to limit exposure.

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-51>= 7.0.0-0, < 7.1.2-26

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. Check installed ImageMagick version
    Run 'convert --version' (for 6.x) or 'magick --version' (for 7.x) to determine the exact version number
    Affected if Version is less than 6.9.13-51 for 6.x, or less than 7.1.2-26 for 7.x (including all 7.0.x versions through 7.1.2-25)
  2. Verify TIFF encoder support is enabled
    Run 'identify -list configure | grep -i tiff' or 'convert -list configure | grep -i tiff' to confirm TIFF support was built into ImageMagick
    Affected if TIFF support is present and the ImageMagick version falls within the affected range
  3. Check for TIFF encoding operations
    Monitor or review logs for active TIFF image processing using ImageMagick (look for 'convert ... tiff' or 'magick ... tiff' operations in process logs)
    Affected if TIFF encoding is being performed using the vulnerable ImageMagick installation
  4. Identify temporary file creation failure conditions
    Check /tmp directory permissions and available disk space. Test with 'touch /tmp/test && rm /tmp/test' to verify write access. Run 'df -h /tmp' to check disk space.
    Affected if The system has restricted /tmp permissions, limited disk space, or other conditions that could cause temporary file creation to fail during TIFF encoding

You are affected if ImageMagick version is less than 6.9.13-51 (6.x) or less than 7.1.2-26 (7.x), TIFF encoding support is enabled, and TIFF processing occurs in an environment where temporary file creation may fail.

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-51 / 7.1.2-26 or later
Fixed in 6.9.13-517.1.2-26
Interim mitigation

Upgrade ImageMagick to version 7.1.2-26 or later (for 7.x), or version 6.9.13-51 or later (for 6.x). If upgrading is not immediately feasible, monitor TIFF processing operations and implement rate limiting on TIFF encoding requests to limit exposure.

Recommended fix High confidence

6.9.13-51 for 6.x branch, or 7.1.2-26 for 7.x branch

  1. Identify your current ImageMagick version using 'convert -version' or 'magick -version'
  2. For ImageMagick 6.x: upgrade to version 6.9.13-51 or later from your distribution's package manager or compile from source
  3. For ImageMagick 7.x: upgrade to version 7.1.2-26 or later from your distribution's package manager or compile from source
  4. Verify the upgrade was successful by checking the new version with 'convert -version' or 'magick -version'
  5. Test TIFF encoding functionality to ensure the upgrade did not break existing workflows
Caveat Review release notes between your current version and the target version for any behavioral changes or removed features

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