CVE-2026-49218
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 · uneditedImageMagick is free and open-source software used for editing and manipulating digital images. Prior to versions 6.9.13-48 and 7.1.2-24, a missing check in the DCM decoder could result in an image with invalid dimensions and that could cause crashes in other operation. This issue has been patched in versions 6.9.13-48 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 confidenceA missing sanity check in ImageMagick's DCM (DICOM medical imaging format) decoder allows processing of image files with invalid dimensions. This can cause crashes when subsequent image operations are performed on the malformed image data.
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< 6.9.13-48>= 7.0.0-0, < 7.1.2-24CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed ImageMagick versionRun `convert --version` (ImageMagick 6) or `magick --version` (ImageMagick 7) and note the version numberAffected if Version is below 6.9.13-48, OR version is 7.0.0-0 through 7.1.2-23 (before 7.1.2-24)
-
Confirm DCM/DICOM coder is availableRun `identify -list format | grep -i dcm` or `identify -list format | grep -i dicom` to see if DCM/DICOM format support is compiled inAffected if DCM or DICOM format appears in the list (indicates the vulnerable decoder is present)
-
Check if DCM files can be processedAttempt to identify a sample DCM file with `identify sample.dcm` or check ImageMagick policy.xml for DCM-related entries under /etc/ImageMagick-6/policy.xml or /etc/ImageMagick/policy.xmlAffected if DCM file type is not explicitly blocked in policy or the identify command successfully reads the file
You are affected if your ImageMagick version falls within the vulnerable ranges (below 6.9.13-48 or 7.0.0-0 through 7.1.2-23) AND the DCM/DICOM decoder is enabled and accessible in your environment.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.9.13-487.1.2-24
Upgrade ImageMagick to version 6.9.13-48 or 7.1.2-24 or later. If upgrade is not immediately feasible, consider disabling DCM file processing or implementing input validation before passing files to ImageMagick.
6.9.13-48 (for 6.x line) or 7.1.2-24 (for 7.x line)
- Check current ImageMagick version: 'convert -version' or 'magick -version'
- For ImageMagick 6.x versions: upgrade to version 6.9.13-48 or later
- For ImageMagick 7.x versions: upgrade to version 7.1.2-24 or later
- Verify the upgrade was successful by running 'convert -version' and confirming the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-49218 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-49218 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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