ImageTragick2: ImageMagick flaws allow arbitrary file read and write via SVG and PostScript
- Severity
- High
- Sources
- 1
What happened
CERT/CC advisory VU580079 (ImageTragick2) describes two variants in ImageMagick: MSL injection via SVG image xlink:href referencing dangerous coders, and Ghostscript invocation through content-based PostScript detection, which permits read/write within /tmp under -dSAFER. CVE-2026-65640 is assigned to variant 2, reported to WordPress. No fixed versions are stated. Updating ImageMagick alone may not suffice; deploy an allowlist policy.xml disabling MSL, MVG, PS, EPS and PDF, isolate untrusted image processing (including AI pipelines), validate content rather than extensions, and alert on policy violations and unexpected delegate use.
For security analysts · Written by AI from 1 source · Wrong?
What to do
- Install vendor-provided updates for any application that integrates ImageMagick, such as Ruby on Rails, WordPress, MediaWiki, ownCloud Classic or Redmine, when available.
- Apply a custom policy.xml based on an allowlist and disable MSL, MVG, PS, EPS and PDF, then confirm prohibited formats are rejected.
- Process untrusted images in a dedicated, minimally privileged environment with restricted filesystem access.
- Alert on ImageMagick policy violations, unexpected coder or delegate use, and unexpected file creation.
Written by AI from the sources, checked against them