CVE-2025-53015

What it actually does

Triggers unbounded resource consumption through an infinite loop that writes lines repeatedly during a specific XMP file conversion operation.

Why it matters to the business

Causes image-processing workloads to hang or exhaust CPU and memory, disrupting services that handle user-supplied images until the process is killed or the host is rebooted.

How an attack unfolds

An attacker supplies a crafted image or XMP metadata to an application that invokes ImageMagick's conversion command; the vulnerable code path enters an infinite write loop, starving the system of resources.

How to fix it

Upgrade ImageMagick to version 7.1.2-0 or later; for source builds, ensure the commit 3fcd081c0278427fc0e8ac40ef75c0a1537792f7 (or equivalent) is included.

How to confirm the fix worked

Confirm the installed version reports 7.1.2-0 or newer; run the affected XMP conversion command against known test images and verify termination within expected time and resource bounds.

Typical attack path

1. Locate an application or service that invokes ImageMagick on untrusted input
2. Craft or obtain an image file that triggers the XMP conversion code path
3. Submit the file through normal upload or processing channels
4. Observe sustained high CPU or memory usage leading to denial of service

How to detect it

Monitor for ImageMagick processes that exhibit sustained high CPU or memory usage during XMP conversion tasks; inspect application and system logs for repeated write operations or unusually long-running convert commands.

What your security team should do

• Apply the fixed version or commit across all ImageMagick installations without delay
• Temporarily disable XMP-related conversion features or sandbox ImageMagick processes if immediate upgrade is not feasible
• Add resource limits and monitoring around all image-processing pipelines