Vulnerability in ImageMagick on Windows (CVE-2026-108693)
Summary
Vulnerability in ImageMagick on Windows (CVE-2026-108693). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
ImageMagick on Windows through 7.1.2-33 and 6.9.13-58 contains an uncontrolled search path vulnerability in NTGhostscriptEXE() that launches gswin64c.exe by bare name when Ghostscript is unregistered. Attackers can plant a malicious gswin64c.exe in the working directory to execute code with ImageMagick privileges when PDF, PostScript, or EPS files are converted.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-108693 has been found in ImageMagick on Windows.
Successful exploitation can lead to full system takeover. CVSS score: 7.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "ImageMagick on Windows CVE-2026-108693" on the vendor's site.
CVE-2026-108693 (ImageMagick on Windows) — CWE-427 / CVSS v3 7.0
Attack vector: local / unauthenticated
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-427) exists in ImageMagick on Windows.
Check the vendor advisory for the affected versions of ImageMagick on Windows.
Severity: High (CVSS 7.0/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで ImageMagick on Windows を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。