dbcve.org
ImagemagickApplication

CVE-2026-61465

MEDIUM · 6.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 →
72/100
Remediation priority · Elevated
Remotely reachable 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-26 and 6.9.13-51 is missing a check for the allowed memory allocation limit in matrix-backed operations such as -canny. An attacker can supply a crafted image that causes ImageMagick to allocate more memory than permitted by the configured policy, resulting in a 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 versions before 7.1.2-26 and 6.9.13-51 lack proper validation of memory allocation limits in matrix-backed operations (e.g., -canny edge detection). Attackers can provide specially crafted images that trigger unbounded memory allocation beyond what the configured security policy permits, causing resource exhaustion and denial of service.

MitigationUpdate ImageMagick to version 7.1.2-26 or later / 6.9.13-51 or later, or ensure the policy.xml file properly restricts memory allocations for the affected operations.

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
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify installed ImageMagick version
    Run 'convert -version' or 'magick -version' to display the installed version string
    Affected if The version shown is before 7.1.2-26 (for 7.x) or before 6.9.13-51 (for 6.x)
  2. Confirm major version branch
    Review the version output to determine if you are running the 6.x or 7.x branch of ImageMagick
    Affected if Running version 7.0.0-0 or later but below 7.1.2-26, or running any 6.x version below 6.9.13-51
  3. Verify matrix-backed operations are available
    Run 'convert -list configure | grep -i canny' or test if '-canny' flag is accepted by the 'convert' command
    Affected if The -canny edge detection or other matrix operations (e.g., -convolve, -morphology) are present and functional in your installation
  4. Inspect security policy for memory limits
    Locate the policy.xml file (commonly at /etc/ImageMagick-6/policy.xml or /etc/ImageMagick-7/policy.xml) and examine the 'memory' and 'map' resource limits within the <policymap> section
    Affected if The policy.xml either lacks explicit memory/map limits, has excessively high limits, or does not restrict the 'coder' or 'filter' resources used by matrix operations

You are affected if your ImageMagick version is below 7.1.2-26 (7.x branch) or below 6.9.13-51 (6.x branch) AND matrix-backed operations like -canny are enabled without restrictive memory policies in place.

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

Update ImageMagick to version 7.1.2-26 or later / 6.9.13-51 or later, or ensure the policy.xml file properly restricts memory allocations for the affected operations.

Recommended fix High confidence

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

  1. 1. Identify the currently installed ImageMagick version using 'convert --version' or 'magick --version'
  2. 2. For ImageMagick 6.x users: Upgrade to version 6.9.13-51 or later from your distribution's package manager or compile from source
  3. 3. For ImageMagick 7.x users: Upgrade to version 7.1.2-26 or later from your distribution's package manager or compile from source
  4. 4. After upgrade, verify the fix by running 'convert --version' to confirm the new version is installed
  5. 5. Test that image processing workflows, particularly those using -canny or other matrix-backed operations, still function correctly
Caveat Minor - this is a bugfix release; verify any custom policy.xml configurations still work as expected after upgrade

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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