dbcve.org
ImagemagickApplication

CVE-2026-48734

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 6.9.13-49 / 7.1.2-24 or later.
See remediation →
58/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 6.9.13-49 and 7.1.2-24, a crafted MVG file could result in a stack overflow due to a missing depth or visited-set check. This issue has been patched in versions 6.9.13-49 and 7.1.2-24.

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 MVG (Magick Vector Graphics) file parser has a stack overflow vulnerability due to missing depth or visited-set checks in versions prior to 6.9.13-49 and 7.1.2-24. A crafted MVG file with deeply nested or recursive elements can exhaust the stack, potentially causing denial of service and possibly enabling code execution.

MitigationUpgrade ImageMagick to version 6.9.13-49 or 7.1.2-24 or later. If MVG processing is not required, disable MVG file handling in the policy configuration as a defense-in-depth measure.

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-49>= 7.0.0-0, < 7.1.2-24

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

CVSS:3.1/AV:L/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. Check installed ImageMagick version
    Run `convert --version` or `magick --version` and note the version number displayed
    Affected if The version is below 6.9.13-49 for the 6.x branch, or below 7.1.2-24 for the 7.x branch, or is any version between 7.0.0-0 and 7.1.2-23
  2. Confirm MVG format support is enabled
    Run `identify -list format | grep -i mvg` or check `magick -list format` output for MVG entries marked as rw (read/write)
    Affected if MVG appears as a supported format with read capability (rw) and is not disabled
  3. Check ImageMagick security policy for MVG restrictions
    Inspect the policy.xml file (typically at /etc/ImageMagick-6/policy.xml or /etc/ImageMagick-7/policy.xml) and look for any `<policy>` entries mentioning 'MVG' or 'mvg'
    Affected if No policy entry exists to restrict or disable MVG file processing, or the policy explicitly allows MVG with pattern '*'
  4. Verify if MVG files can be processed
    Attempt to identify a simple MVG file using `identify <file.mvg>` if you have a test MVG file available, or check if the MVG coder is loaded by running `magick -list configure | grep -i mvg`
    Affected if The MVG coder is loaded and functional, allowing MVG file processing

You are affected if your installed ImageMagick version falls within the vulnerable ranges AND MVG file processing is enabled and not restricted by policy.

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-49 / 7.1.2-24 or later
Fixed in 6.9.13-497.1.2-24
Interim mitigation

Upgrade ImageMagick to version 6.9.13-49 or 7.1.2-24 or later. If MVG processing is not required, disable MVG file handling in the policy configuration as a defense-in-depth measure.

Recommended fix High confidence

ImageMagick 6.9.13-49 or 7.1.2-24 (or later)

  1. Check the current ImageMagick version installed (e.g., `convert --version` or `magick --version`)
  2. Determine whether you are using the 6.x or 7.x branch based on the current version
  3. For package manager installations (apt/yum/dnf), update the package repository and upgrade ImageMagick: `sudo apt update && sudo apt install imagemagick` or `sudo dnf update imagemagick`
  4. If building from source, download ImageMagick 6.9.13-49 or 7.1.2-24 (or later) from the official source and rebuild
  5. Verify the upgrade was successful by checking the new version matches or exceeds the fixed releases
  6. Test that any image processing workflows using MVG files continue to function as expected

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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