dbcve.org
ImagemagickApplication

CVE-2026-53467

MEDIUM · 5.3 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 →
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 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, the MNG decoder contains a possible heap information disclosure vulnerability because part of the pixels are left unchanged. 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's MNG (Multiple-image Network Graphics) decoder has a heap information disclosure vulnerability in versions prior to 6.9.13-51 and 7.1.2-26. During MNG image processing, some pixel data is not properly initialized or cleared, causing residual heap memory contents to potentially appear in the output image. This could expose sensitive data from previous memory operations to users who process MNG files.

MitigationUpgrade ImageMagick to version 6.9.13-51 or later (6.x) or 7.1.2-26 or later (7.x). If immediate upgrading is not feasible, disable MNG format processing in ImageMagick configurations or use content filtering to reject MNG files.

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
Low
Integrity
None
Availability
None

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

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 `identify -version` or `magick --version` to see the exact version number
    Affected if Version is below 6.9.13-51 for 6.x, or below 7.1.2-26 for 7.x versions
  2. Verify MNG format support is enabled
    Run `identify -list format | grep -i mng` to see if MNG is listed as supported
    Affected if MNG appears in the list of supported formats with 'rw' or 'rw+' permissions (indicating read/write capability)
  3. Check ImageMagick policy.xml for MNG restrictions
    Locate the policy.xml file (commonly in /etc/ImageMagick-6 or /etc/ImageMagick-7) and search for any `<policy>` entries mentioning MNG
    Affected if There is no policy blocking or restricting MNG format processing (i.e., MNG is not explicitly disabled)
  4. Identify MNG file processing in your environment
    Search for .mng or .mng-like files in your data directories, or review application logs that process image files
    Affected if MNG files are present or processed by systems using the vulnerable ImageMagick version

You are affected if your ImageMagick version falls in the vulnerable range AND MNG format support is enabled AND your systems process MNG files, allowing uninitialized heap memory to leak into output 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 6.9.13-51 or later (6.x) or 7.1.2-26 or later (7.x). If immediate upgrading is not feasible, disable MNG format processing in ImageMagick configurations or use content filtering to reject MNG files.

Recommended fix High confidence

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

  1. Check current ImageMagick version using 'convert -version' or 'magick -version'
  2. If using ImageMagick 6.x (e.g., 6.9.13-50 or earlier), upgrade to version 6.9.13-51 or later using your system's package manager
  3. If using ImageMagick 7.x (e.g., 7.0.0-0 through 7.1.2-25), upgrade to version 7.1.2-26 or later using your system's package manager
  4. Verify the upgrade was successful by running 'convert -version' or 'magick -version' and confirming the installed version is >= the fixed release for your major version branch
  5. Test any image processing workflows that involve MNG files to ensure functionality is intact
Caveat Minimal expected; this is a security patch. Note that upgrading from ImageMagick 6.x to 7.x may introduce breaking API/behavior changes if you have custom code relying on 6.x-specific behavior.

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
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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