Read the docs

Policy bypass in ImageMagick when policy.xml DOCTYPE is changed

Priority LOW 34CWE-693Published · Updated

Key facts

Attack vector
Local
Privileges required
High
User interaction
None
Attack complexity
High
Impact type
Security bypass
Confidentiality · integrity · availability
Low · Low · Low
Fix status
Fixed

Attack profile from CVSS 3.1 · GHSA-jjp4-3fwf-393j. Fix status from GitHub. Impact type from CWE-693.

Summary

ImageMagick versions before 7.1.2-32 and before 6.9.13-57 are affected. When a user changes the DOCTYPE in policy.xml to another valid XML DOCTYPE, the security policy is not applied (CWE-693). A local attacker with high privileges can bypass the policy, with low impact on confidentiality, integrity and availability.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

When a user changes the DOCTYPE in the policy.xml file to something else that is valid xml the security policy will not be applied.

Why it matters now

Fix Fixed ImageMagick (c/c++): 7.1.2-32, 6.9.13-57

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—ImageMagick (c/c++)< 7.1.2-327.1.2-32Patch availableGHSA-jjp4-3fwf-393j
—ImageMagick (c/c++)< 6.9.13-576.9.13-57Patch availableGHSA-jjp4-3fwf-393j
  • ImageMagick (c/c++) Vendor— Affected < 7.1.2-32 Fixed in 7.1.2-32 Patch available GHSA-jjp4-3fwf-393j
  • ImageMagick (c/c++) Vendor— Affected < 6.9.13-57 Fixed in 6.9.13-57 Patch available GHSA-jjp4-3fwf-393j

Remediation

Upgrade ImageMagick 7.x to version 7.1.2-32 and ImageMagick 6.x to version 6.9.13-57, which fix the issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-jjp4-3fwf-393j ImageMagick (c/c++) Fixed in 7.1.2-32 Advisory →
  • Fix · GHSA-jjp4-3fwf-393j ImageMagick (c/c++) Fixed in 6.9.13-57 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-jjp4-3fwf-393j

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences