dbcve.org
ImagemagickApplication

CVE-2026-28690

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 6.9.13-41 / 7.1.2-16 or later.
See remediation →
68/100
Remediation priority · Elevated
No privileges

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 7.1.2-16 and 6.9.13-41, a stack buffer overflow vulnerability exists in the MNG encoder. There is a bounds checks missing that could corrupting the stack with attacker-controlled data. This vulnerability is fixed in 7.1.2-16 and 6.9.13-41.

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

A stack buffer overflow vulnerability exists in ImageMagick's MNG encoder due to missing bounds checks. This allows attacker-controlled data to corrupt the stack, potentially leading to code execution or denial of service. The vulnerability affects versions prior to 7.1.2-16 and 6.9.13-41.

MitigationUpgrade ImageMagick to version 7.1.2-16/6.9.13-41 or later. If upgrading is not feasible, consider disabling MNG format processing in ImageMagick configuration.

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-41>= 7.0.0-0, < 7.1.2-16

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

CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:H/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 installed ImageMagick version
    Run 'magick --version' or 'convert --version' to retrieve the version number
    Affected if Version is below 6.9.13-41 (6.x branch) or below 7.1.2-16 (7.x branch)
  2. Identify MNG format support in ImageMagick
    Run 'magick -list format' or check 'ConfigureScript' output for MNG module (libmng or MNG codec)
    Affected if MNG format is listed as 'r--r--r--' (read support present) or the MNG delegate library is loaded
  3. Verify MNG encoder is available
    Check for 'MNG' in the output of 'magick -list configure' under DELEGATES, or examine /usr/lib/ImageMagick-* modules for mng.so/mng.la
    Affected if The MNG delegate library (libmng) is linked and the encoder module exists in the module path

Environment is affected if ImageMagick version is below the fixed releases AND MNG format processing is enabled (the MNG encoder module is loaded and MNG is a recognized format).

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-41 / 7.1.2-16 or later
Fixed in 6.9.13-417.1.2-16
Interim mitigation

Upgrade ImageMagick to version 7.1.2-16/6.9.13-41 or later. If upgrading is not feasible, consider disabling MNG format processing in ImageMagick configuration.

Recommended fix High confidence

ImageMagick 7.1.2-16 (or later) for 7.x branch; ImageMagick 6.9.13-41 (or later) for 6.x branch

  1. Identify your current ImageMagick version using 'convert -version' or 'magick -version'
  2. For ImageMagick 7.x users: Upgrade to version 7.1.2-16 or later
  3. For ImageMagick 6.x users: Upgrade to version 6.9.13-41 or later
  4. On Debian/Ubuntu: Use 'apt-get update && apt-get install imagemagick' or download from source
  5. On RHEL/CentOS: Use 'yum update ImageMagick' or 'dnf update ImageMagick'
  6. On macOS: Use 'brew upgrade imagemagick' if installed via Homebrew
  7. Verify the upgrade was successful by checking the version again
  8. Test that your image processing workflows function correctly with the new version
Caveat Review release notes for any behavioral changes between your current version and the fixed version, particularly in MNG format handling

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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