dbcve.org
ImagemagickApplication

CVE-2026-48724

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-10
Fix available
A fix is available. Upgrade to 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 version 7.1.2-24, when using an image with mask the Floyd-Steinberg dithering method it will cause a negative heap buffer over-write. This issue has been patched in version 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 · moderate confidence

ImageMagick versions prior to 7.1.2-24 contain a memory corruption vulnerability in the Floyd-Steinberg dithering implementation. When processing an image with a mask using this dithering method, a negative index is used in a heap buffer write operation, potentially allowing memory corruption that could lead to denial of service or potentially arbitrary code execution.

MitigationUpgrade ImageMagick to version 7.1.2-24 or later to obtain the patched version. Avoid processing untrusted images with Floyd-Steinberg dithering and masks until the upgrade is applied.

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:< 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. Verify ImageMagick is installed
    Run `which convert` or `which magick` to locate the ImageMagick binary
    Affected if No ImageMagick binary is found on the system
  2. Determine installed ImageMagick version
    Run `convert -version` or `magick -version` and note the version number in the output (e.g., 7.1.2-20)
    Affected if The version number is lower than 7.1.2-24
  3. Check for ImageMagick in application dependencies
    Review application dependency files (e.g., package.json, requirements.txt, Gemfile, pom.xml) or system package manager listings (dpkg -l, rpm -qa) for ImageMagick version declarations
    Affected if Any declared ImageMagick version is earlier than 7.1.2-24
  4. Identify use of Floyd-Steinberg dithering with masks
    Search codebase and configuration files for dither-related parameters such as `-dither`, `-floyd-steinberg`, or `-ordered-dither` combined with mask operations (e.g., `-mask`, compose operations with alpha channels)
    Affected if Any image processing scripts, programs, or configs use Floyd-Steinberg dithering in combination with mask operations on user-supplied images

ImageMagick is affected if version is below 7.1.2-24 AND the system processes untrusted images using Floyd-Steinberg dithering together with mask operations.

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

Upgrade ImageMagick to version 7.1.2-24 or later to obtain the patched version. Avoid processing untrusted images with Floyd-Steinberg dithering and masks until the upgrade is applied.

Recommended fix High confidence

7.1.2-24 or later

  1. Check current ImageMagick version: convert --version
  2. Upgrade ImageMagick to version 7.1.2-24 or later using your package manager (e.g., apt-get update && apt-get install imagemagick, yum update imagemagick, or brew upgrade imagemagick)
  3. Alternatively, compile from source: download from https://github.com/ImageMagick/ImageMagick/releases/tag/7.1.2-24 or later
  4. Verify the upgrade was successful: convert --version
Caveat Minor version upgrades may include behavior changes; review release notes if using in production

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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