dbcve.org
ImagemagickApplication

CVE-2026-56365

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-30
Fix available
A fix is available. Upgrade to 6.9.13-44 / 7.1.2-19 or later.
See remediation →
62/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 before 7.1.2-19 contains a memory leak vulnerability in the PNG encoder when writing MNG images. Attackers can trigger the encoder failure condition to exhaust memory resources 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 · moderate confidence

ImageMagick versions prior to 7.1.2-19 contain a memory leak in the PNG encoder that is triggered when writing MNG (Multiple-image Network Graphics) format files. Attackers can exploit this by providing specially crafted input that causes the encoder to fail in a way that leaks memory, leading to resource exhaustion and denial of service.

MitigationUpgrade ImageMagick to version 7.1.2-19 or later to patch the memory leak. If upgrade is not immediately feasible, restrict or disable MNG format processing in ImageMagick configurations and monitor for anomalous memory consumption from ImageMagick processes.

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-44>= 7.0.0-0, < 7.1.2-19

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 'magick -version' or 'identify -version' to retrieve the exact version number of ImageMagick installed on the system
    Affected if The version is less than 6.9.13-44, or is 7.0.0-0 through 7.1.2-18 (meaning versions prior to 7.1.2-19)
  2. Confirm MNG format support is enabled
    Check ImageMagick configuration by running 'magick -list format' and look for MNG in the output, or check policy.xml configuration files for MNG-related entries
    Affected if MNG format shows as ' rw+' or ' rw' (read-write) in the format list, indicating support is enabled
  3. Identify MNG file processing activity
    Review application logs, web server logs, or ImageMagick command history for any recent operations involving .mng or .mng-format output
    Affected if Any MNG files have been written or processed recently using the ImageMagick installation
  4. Monitor for anomalous memory behavior
    Observe memory usage of ImageMagick processes using tools like 'ps' or process monitors, particularly those that have processed MNG files
    Affected if ImageMagick processes show unexpectedly high or growing memory consumption that does not decrease after processing completes

You are affected if your ImageMagick version falls within the vulnerable range (prior to 6.9.13-44 or 7.0.0-0 through 7.1.2-18) AND MNG format support is enabled AND MNG files are being processed.

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-44 / 7.1.2-19 or later
Fixed in 6.9.13-447.1.2-19
Interim mitigation

Upgrade ImageMagick to version 7.1.2-19 or later to patch the memory leak. If upgrade is not immediately feasible, restrict or disable MNG format processing in ImageMagick configurations and monitor for anomalous memory consumption from ImageMagick processes.

Recommended fix High confidence

ImageMagick 7.1.2-19 or later (7.x branch); ImageMagick 6.9.13-44 or later (6.x branch)

  1. 1. Identify the current ImageMagick version installed on the system using 'convert --version' or 'magick --version'
  2. 2. For ImageMagick 7.x users: Upgrade to version 7.1.2-19 or later
  3. 3. For ImageMagick 6.x users: Upgrade to version 6.9.13-44 or later
  4. 4. Verify the upgrade was successful by running 'convert --version' and confirming the version number matches the fixed release
  5. 5. Test any image processing workflows that involve MNG files to ensure functionality is intact

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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