Security readout for executives and security teams
Plain-English summary
ImageMagick can be forced to request an extremely large memory allocation when handling a crafted SVG. Systems that process attacker-supplied images may crash or lose availability. The source bundle names patched ImageMagick releases, but provides no evidence of active exploitation.
Executive priority
Prioritize patching internet-facing or customer-upload image workflows. Treat this as a high availability risk, especially for shared processing infrastructure where crashes can disrupt multiple services.
Technical view
Before ImageMagick 7.1.2-15 and 6.9.13-40, the internal SVG decoder lacks sufficient allocation limits. A crafted SVG element can cause an attempted allocation of about 674 GB, leading to an out-of-memory abort. The issue maps to CWE-770 and CWE-789 and is availability-only under CVSS 3.1.
Likely exposure
Exposure is most likely in web apps, batch processors, CMS pipelines, or security tools that invoke affected ImageMagick versions on untrusted or user-uploaded SVG files.
Exploitation context
The bundle reports KEV as false and includes no cited evidence of active exploitation. The documented impact is denial of service through resource exhaustion, not code execution or data theft.
Researcher notes
The evidence supports a resource-exhaustion flaw in ImageMagick's internal SVG decoding path. The bundle does not provide proof-of-concept details beyond the excessive allocation behavior, and does not indicate confidentiality, integrity, or active exploitation impact.
Mitigation direction
- Upgrade ImageMagick 7.x to 7.1.2-15 or later.
- Upgrade ImageMagick 6.x to 6.9.13-40 or later.
- Apply applicable vendor packages, including Red Hat advisory RHSA-2026:5573 where relevant.
- Limit or block untrusted SVG processing until patched.
- Review image-processing workers for memory and restart controls.
Validation and detection
- Inventory hosts and containers running ImageMagick.
- Check installed ImageMagick versions against the affected ranges.
- Identify services that accept SVG uploads or process external images.
- Confirm vendor package status for Red Hat-managed systems.
- Verify patched versions are deployed in production images.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCWE-789: 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.
Open ATT&CK lookupCVE-2026-25985 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
2 official scoresWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6GitHub_MCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat-SADPVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- ADP timelineredhat-SADP
Made public.
- CVE publishedCVE Program
The CVE record was published.
- ADP timelineredhat-SADP
Reported to Red Hat.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
- 2026-02-24T02:02:48.034Z: Reported to Red Hat.
- 2026-02-24T01:43:07.076Z: Made public.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/ImageMagick/ImageMagick/security/advisories/GHSA-v7g2-m8c5-mf84CVE reference, GitHub_M · x_refsource_CONFIRM
- https://access.redhat.com/security/cve/CVE-2026-25985CVE reference, redhat-SADP · vdb-entry, x_refsource_REDHAT
- RHBZ#2442127CVE reference, redhat-SADP · issue-tracking, x_refsource_REDHAT
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25985.jsonCVE reference, redhat-SADP · x_sadp-csaf-vex
- https://access.redhat.com/errata/RHSA-2026:5573CVE reference, redhat-SADP · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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
Memory Allocation with Excessive Size Value represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.