dbcve.org
ImagemagickApplication

CVE-2026-55577

MEDIUM · 5.9 CVSS v3.1 Published 2026-07-01
Fix available
A fix is available. Upgrade to 6.9.13-51 / 7.1.2-26 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 7 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 is free and open-source software used for editing and manipulating digital images. Prior to versions 6.9.13-51 and 7.1.2-26, a heap buffer overflow occurs in the MVG decoder that could result in an out of bounds write when processing a crafted image. This issue has been fixed in versions 6.9.13-51 and 7.1.2-26.

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 6.9.13-51 and 7.1.2-26 contain a heap buffer overflow vulnerability in the MVG (Magick Vector Graphics) decoder. When processing a specially crafted malicious image file, the decoder writes data beyond allocated heap memory boundaries, potentially leading to memory corruption, denial of service, or possible code execution.

MitigationUpgrade ImageMagick to version 6.9.13-51 or 7.1.2-26 or later. If immediate patching is not feasible, consider disabling MVG file format processing or restricting ImageMagick's ability to process untrusted images in the affected systems.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/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. Identify installed ImageMagick version
    Run 'convert -version' or 'magick -version' to display the installed version number. Compare the major.minor.patch values against the affected ranges: versions below 6.9.13-51, or versions 7.0.0-0 through 7.1.2-25.
    Affected if The installed version falls below 6.9.13-51 or is between 7.0.0-0 and 7.1.2-25 inclusive.
  2. Confirm MVG decoder is available
    Run 'convert -list configure | grep -i mvg' or check if the MVG format is listed in 'convert -list format'. The MVG format must be present and not explicitly disabled for the vulnerability to be triggerable.
    Affected if MVG format support is enabled and listed in available decoders.
  3. Check ImageMagick security policy
    Inspect the policy.xml file (commonly in /etc/ImageMagick-6/ or /etc/ImageMagick-7/) for any <policy> entries that restrict or disable the MVG coder. Look for patterns like '<policy domain="coder" rights="none" pattern="MVG"/>'.
    Affected if No policy explicitly blocks MVG processing, or the policy file is missing entirely.
  4. Verify ability to process untrusted image files
    Check if ImageMagick is configured to process files from untrusted sources, such as web applications, email attachments, or user-uploaded content. Review application or system configurations that invoke ImageMagick commands.
    Affected if ImageMagick can be invoked to process files from untrusted or external sources without additional validation.

A system is affected if it runs a vulnerable ImageMagick version with MVG support enabled and can process untrusted MVG image 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-51 / 7.1.2-26 or later
Fixed in 6.9.13-517.1.2-26
Interim mitigation

Upgrade ImageMagick to version 6.9.13-51 or 7.1.2-26 or later. If immediate patching is not feasible, consider disabling MVG file format processing or restricting ImageMagick's ability to process untrusted images in the affected systems.

Recommended fix High confidence

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

  1. Check current ImageMagick version using 'convert --version' or 'magick --version'
  2. For ImageMagick 6.x users: upgrade to version 6.9.13-51 or later
  3. For ImageMagick 7.x users: upgrade to version 7.1.2-26 or later
  4. Verify the upgrade was successful by checking the version again
  5. Test critical image processing workflows to ensure functionality is intact
Caveat Review release notes for any backward compatibility changes in the new version

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 / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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