CVE-2026-24484
Denial of Service in ImageMagick via Nested MVG to SVG Conversion
Publication date: 2026-02-24
Last updated on: 2026-02-27
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| imagemagick | imagemagick | to 6.9.13-40 (exc) |
| imagemagick | imagemagick | From 7.0.0-0 (inc) to 7.1.2-15 (exc) |
| dlemstra | magick.net | to 14.10.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-400 | The product does not properly control the allocation and maintenance of a limited resource. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-24484 is a vulnerability in ImageMagick related to the processing of multi-layer nested MVG (Magick Vector Graphics) conversions to SVG format. The issue occurs because ImageMagick fails to properly check the recursion depth when handling nested "graphic-context" tokens in SVG images. This can lead to excessive recursion depth, causing resource exhaustion or a denial of service (DoS) condition.'}, {'type': 'paragraph', 'content': 'The vulnerability specifically arises in the WriteSVGImage function within the SVG image coder, where deeply nested vector graphics can cause stack overflow or crashes. The patch for this vulnerability adds a recursion depth check that throws an error if the nesting exceeds a predefined limit, preventing the excessive resource consumption.'}] [1, 2]
How can this vulnerability impact me? :
This vulnerability can be exploited remotely without any privileges or user interaction, leading to a denial of service (DoS) condition. The impact is on availability, as the system running ImageMagick may crash or become unresponsive due to excessive resource consumption caused by processing deeply nested SVG content.
It does not affect confidentiality or integrity of data, but the service disruption could impact applications or services relying on ImageMagick for image processing.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': 'This vulnerability in ImageMagick relates to excessive recursion depth when processing nested MVG to SVG conversions, which can lead to denial of service. Detection involves identifying attempts to process SVG images with deeply nested "graphic-context" tokens that may trigger the vulnerability.'}, {'type': 'paragraph', 'content': 'Since the issue is triggered by specific crafted SVG or MVG files, one way to detect exploitation attempts is to monitor logs or application behavior for errors or crashes related to SVG processing, especially errors mentioning "VectorGraphicsNestedTooDeeply" if the patched version is in use.'}, {'type': 'paragraph', 'content': 'There are no explicit commands provided in the resources to detect this vulnerability directly on a network or system. However, you can check the installed ImageMagick version to determine if it is vulnerable by running:'}, {'type': 'list_item', 'content': 'magick -version'}, {'type': 'paragraph', 'content': 'If the version is prior to 7.1.2-15 or 6.9.13-40, it is vulnerable. Additionally, monitoring for unusual resource consumption or crashes during image processing involving SVG or MVG files may indicate exploitation attempts.'}] [1, 2]
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade ImageMagick to a patched version that addresses this vulnerability.
- Upgrade to ImageMagick version 7.1.2-15 or later, or 6.9.13-40 or later.
- If using Magick.NET, upgrade to version 14.10.3 or later, which includes the relevant security fixes.
These updates include a patch that enforces a recursion depth limit during SVG image writing, preventing denial of service caused by deeply nested vector graphics.
Until the upgrade can be applied, consider restricting or monitoring the processing of untrusted SVG or MVG files to reduce the risk of exploitation.