CVE-2026-25985: Memory allocation with excessive without limits in the internal SVG decoder
ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to versions 7.1.2-15 and 6.9.13-40, a crafted SVG file containing an malicious element causes ImageMagick to attempt to allocate ~674 GB of memory, leading to an out-of-memory abort. Versions 7.1.2-15 and 6.9.13-40 contain a patch.
Security readout for executives and security teams
Plain-English summary
A malicious SVG processed by vulnerable ImageMagick can force a huge memory allocation, causing the process or host to run out of memory. The disclosed impact is denial of service, not data theft or code execution. Fixed versions are available.
Executive priority
Prioritize remediation for internet-facing or customer-facing image processing. The issue can disrupt availability with low attacker requirements, but current sources do not show active exploitation or data compromise.
Technical view
Before ImageMagick 7.1.2-15 and 6.9.13-40, the internal SVG decoder lacked sufficient allocation limits. A crafted SVG element could trigger an attempted allocation of about 674 GB, leading to out-of-memory abort. CVSS is 7.5, availability-only high impact.
Likely exposure
Exposure is most likely where affected ImageMagick versions process untrusted SVG input, such as automated image conversion, upload handling, or thumbnail generation pipelines. Source data does not identify specific downstream applications beyond ImageMagick.
Exploitation context
The provided sources do not state active exploitation, and KEV is false. The practical scenario is denial of service by causing an affected ImageMagick process to parse a crafted SVG. No source supports confidentiality or integrity impact.
Researcher notes
Focus validation on SVG decoding paths and memory control boundaries. The record maps to CWE-770 and CWE-789. Avoid assuming broader ImageMagick formats or code execution without additional evidence.
Mitigation direction
Upgrade ImageMagick to 7.1.2-15, 6.9.13-40, or later.
Apply applicable vendor updates, including Red Hat advisories where relevant.
Restrict or disable untrusted SVG processing until patched.
Use resource limits for image processing workloads.
Monitor vendor guidance for distribution-specific package status.
Validation and detection
Inventory ImageMagick versions across servers, containers, and build images.
Check whether services accept or transform SVG files from untrusted users.
Confirm deployed packages meet 7.1.2-15 or 6.9.13-40 minimums.
Review logs for image-processing crashes or out-of-memory events.
Verify Red Hat package status against RHSA-2026:5573 where applicable.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-770 · source CWE mapping
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Memory Allocation with Excessive Size Value represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.