CVE-2025-55298

What it actually does

Format string vulnerability in InterpretImageFilename allows unsanitized user input to reach FormatLocaleString, enabling arbitrary memory writes that can escalate from heap corruption to remote code execution.

Why it matters to the business

Applications relying on ImageMagick for image handling face risk of full system compromise, potentially disrupting image-processing workflows and exposing sensitive data across dependent services.

How an attack unfolds

An attacker supplies a crafted filename, metadata, or image path containing format specifiers that reach InterpretImageFilename; the unsanitized string is passed to FormatLocaleString, corrupting memory and achieving code execution without authentication.

How to fix it

Upgrade to ImageMagick 6.9.13-28 or 7.1.2-2. For GIT builds apply commits 439b362b93c074eea6c3f834d84982b43ef057d5 (main) or 2fe4a1049f469029878b05426cbbf652a94006f8 (6 branch).

How to confirm the fix worked

Verify installed version against 6.9.13-28 / 7.1.2-2 or confirm presence of the listed git commits; test with known format-string payloads in controlled environments to ensure crashes no longer occur.

Typical attack path

1. Identify a target application accepting image uploads or filenames processed by ImageMagick
2. Craft malicious input embedding format string specifiers in filename or metadata
3. Trigger processing through InterpretImageFilename to invoke FormatLocaleString
4. Achieve memory overwrite leading to control-flow hijacking or RCE
5. Execute payload to establish persistence or exfiltrate data

How to detect it

Review application and system logs for calls to InterpretImageFilename or FormatLocaleString with unusual filename arguments; inspect image-processing service logs for segmentation faults or memory-corruption signals around image handling.

• InterpretImageFilename
• FormatLocaleString

What your security team should do

• Immediately upgrade all ImageMagick instances to the patched versions
• Scan codebases and containers for references to affected GIT revisions
• Implement input sanitization or filename whitelisting around image processing paths
• Monitor EPSS trend and reassess exploit maturity weekly