dbcve.org
ImagemagickApplication

CVE-2026-25982

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-24
Fix available
A fix is available. Upgrade to 6.9.13-40 / 7.1.2-15 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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-15 and 6.9.13-40, a heap out-of-bounds read vulnerability exists in the `coders/dcm.c` module. When processing DICOM files with a specific configuration, the decoder loop incorrectly reads bytes per iteration. This causes the function to read past the end of the allocated buffer, potentially leading to a Denial of Service (crash) or Information Disclosure (leaking heap memory into the image). Versions 7.1.2-15 and 6.9.13-40 contain a patch.

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

Heap out-of-bounds read vulnerability in ImageMagick's DICOM image decoder (coders/dcm.c). When processing DICOM files with a specific configuration, the decoder loop incorrectly reads bytes per iteration, causing reads past the end of the allocated buffer. This can result in denial of service (crash) or information disclosure by leaking heap memory into the rendered image.

MitigationUpgrade ImageMagick to version 7.1.2-15 / 6.9.13-40 or later to patch the vulnerable DICOM decoder. If upgrading is not immediately feasible, restrict or validate DICOM file processing inputs.

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-40>= 7.0.0-0, < 7.1.2-15

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 `convert --version` or `magick --version` to determine the exact version number
    Affected if The version is below 6.9.13-40, or is 7.0.0-0 through 7.1.2-14 (inclusive)
  2. Verify DICOM coder is available
    Run `convert -list configure | grep -i dcm` or check if the dcm coder is listed in the output of `convert -list coders`
    Affected if The DICOM coder (DCM) appears in the list of available coders, indicating the decoder is present and loadable
  3. Check if DICOM delegate library is installed
    Run `convert -list configure | grep -i delegate` and look for dicom/dcm entries, or check for libdcmtk packages on the system
    Affected if DICOM delegate support is compiled into ImageMagick, meaning the vulnerable decoder code path can be triggered
  4. Identify active ImageMagick policy restrictions
    Check /etc/ImageMagick-6/policy.xml or /etc/ImageMagick-7/policy.xml (or `convert -list policy`) for any coder restrictions on DCM
    Affected if The DCM coder is NOT explicitly disabled in the policy, meaning DICOM files can be processed
  5. Detect recent DICOM file processing activity
    Review application logs, web server logs, or file access patterns for .dcm or .dicom file processing requests
    Affected if The environment processes DICOM files or has recent evidence of DICOM decoding activity

You are affected if your ImageMagick version falls within the vulnerable ranges AND the DICOM coder is enabled and accessible in your environment.

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-40 / 7.1.2-15 or later
Fixed in 6.9.13-407.1.2-15
Interim mitigation

Upgrade ImageMagick to version 7.1.2-15 / 6.9.13-40 or later to patch the vulnerable DICOM decoder. If upgrading is not immediately feasible, restrict or validate DICOM file processing inputs.

Recommended fix High confidence

ImageMagick 6.9.13-40 (for 6.x branch) or ImageMagick 7.1.2-15 (for 7.x branch)

  1. Check current ImageMagick version using 'convert -version' or 'magick -version'
  2. If running ImageMagick 6.x (version < 6.9.13-40), upgrade to version 6.9.13-40 or later
  3. If running ImageMagick 7.x (version >= 7.0.0-0 and < 7.1.2-15), upgrade to version 7.1.2-15 or later
  4. On RHEL/CentOS/Fedora: sudo yum update ImageMagick or sudo dnf update ImageMagick
  5. On Debian/Ubuntu: sudo apt update && sudo apt install imagemagick
  6. On macOS with Homebrew: brew upgrade imagemagick
  7. On Alpine: apk add --upgrade imagemagick
  8. Verify the new version is installed: convert -version

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

Fix this in Imagemagick Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,200
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,520.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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