Vulnerability in Imagemagick (CVE-2026-105083)
Summary
Vulnerability in Imagemagick (CVE-2026-105083). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
ImageMagick before 7.1.2-32 and 6.9.13-57 contains a policy bypass vulnerability in LoadPolicyCache that silently skips security policy rules when policy.xml uses an alternate DOCTYPE. A valid DOCTYPE not ending in ']>' makes the parser consume the rest of the file, so no policy rules are applied and restricted operations become allowed.
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-105083 has been found in Imagemagick.
Risk of unauthorized operations or information disclosure. CVSS score: 3.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Imagemagick CVE-2026-105083" on the vendor's site.
CVE-2026-105083 (Imagemagick) — CWE-693 / CVSS v3 3.9
Attack vector: local / no user interaction
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-693) exists in Imagemagick.
Check the vendor advisory for the affected versions of Imagemagick.
Severity: Low (CVSS 3.9/10). Risk of unauthorized operations or information disclosure.
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. Run grep -r 'Imagemagick' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Imagemagick' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Imagemagickを grep し、稼働しているサービス・バージョンを把握する。 -
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- patch disclosure@vulncheck.com
- patch disclosure@vulncheck.com
- patch disclosure@vulncheck.com
- patch disclosure@vulncheck.com
- patch disclosure@vulncheck.com
- patch disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web disclosure@vulncheck.com
- web nvd.nist.gov
- web github.com