dbcve.org
ImagemagickApplication

CVE-2026-61870

HIGH · 7.5 CVSS v3.1 Published 2026-07-11
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 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-26 contains a memory leak vulnerability in the VIFF encoder when memory allocation fails. Attackers can trigger allocation failures by processing specially crafted VIFF images to exhaust available memory and cause denial of service.

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 before 7.1.2-26 contains a memory leak in the VIFF image format encoder. When memory allocation fails during processing of specially crafted VIFF images, allocated memory is not properly freed, allowing attackers to exhaust system memory and cause denial of service.

MitigationUpgrade ImageMagick to version 7.1.2-26 or later to patch the memory leak in the VIFF encoder. If VIFF processing is not required, consider disabling the VIFF coder as a defense-in-depth measure.

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 ImageMagick version
    Run `convert --version` or `magick --version` to display the installed version number
    Affected if The version is below 6.9.13-51, or is 7.0.0.0 or above but below 7.1.2-26
  2. Verify VIFF coder availability
    Run `convert -list coder` or `magick -list coder` to list supported image formats and check if VIFF/VIF is listed
    Affected if VIFF coder is present and available for image processing
  3. Confirm VIFF format support in configuration
    Run `convert -list configure` and examine the output for VIFF-related configuration flags or coder paths
    Affected if VIFF support is compiled in or dynamically loaded as a module
  4. Check if VIFF is used in policy or delegates
    Inspect /etc/ImageMagick-6/policy.xml or /etc/ImageMagick-7/policy.xml (or the active policy file) for any VIFF-related restrictions or delegate definitions
    Affected if VIFF format is allowed or has delegate handlers defined without explicit blocking
  5. Test VIFF decoding capability
    Attempt to identify a VIFF format file using `identify <file.viff>` or check coder support with `convert logo.miff viff:output.viff` to confirm encoder loads
    Affected if The VIFF coder can be invoked without errors, indicating the vulnerable encoder code path exists

You are affected if your ImageMagick version falls within the vulnerable ranges (below 6.9.13-51 or below 7.1.2-26) AND the VIFF coder is enabled and capable of processing VIFF images.

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 to patch the memory leak in the VIFF encoder. If VIFF processing is not required, consider disabling the VIFF coder as a defense-in-depth measure.

Recommended fix High confidence

ImageMagick 7.1.2-26 (or later) for 7.x branch; ImageMagick 6.9.13-51 (or later) for 6.x branch

  1. 1. Identify the currently installed ImageMagick version using 'convert --version' or 'magick --version'
  2. 2. For ImageMagick 7.x users: Upgrade to version 7.1.2-26 or later
  3. 3. For ImageMagick 6.x users: Upgrade to version 6.9.13-51 or later
  4. 4. On Linux/Unix systems, use your package manager (e.g., 'apt-get update && apt-get install imagemagick' or 'yum update imagemagick') or compile from source
  5. 5. On Windows, download and install the latest version from imagemagick.org
  6. 6. Verify the fix by running 'convert --version' and confirming the installed version is at least 6.9.13-51 (6.x) or 7.1.2-26 (7.x)
  7. 7. Test that ImageMagick can process VIFF images without memory leaks
Caveat Major version upgrades may introduce backward-incompatible changes; review release notes before upgrading production systems

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