Cyber Resilience

CVE-2026-29074

Svgo 2.1.0 – 2.8.1

Public PoC
Published
06 March 2026
Modified
12 August 2026
Patch / advisory
View advisory
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS Score 0.0061 46th percentile
Risk Priority 58 floored blend · peak EPSS

Summary

CVE-2026-29074 is a high-severity XML Entity Expansion (CWE-776) vulnerability in Svgo Svgo. Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 46th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-29074 is a denial-of-service vulnerability in SVGO, a Node.js library and command-line application for optimizing SVG files. Published on 2026-03-06, it affects versions from 2.1.0 to before 2.8.1, from 3.0.0 to before 3.3.3, and before 4.0.1. The flaw stems from SVGO accepting XML with custom entities without protections against entity expansion or recursion, enabling a small 811-byte XML file to trigger excessive memory usage. It carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) and maps to CWE-776.

Any unauthenticated remote attacker can exploit this vulnerability by supplying a malicious SVG file to an application or service using a vulnerable SVGO version. No user interaction or privileges are required, and exploitation is straightforward due to low attack complexity. Successful exploitation stalls the targeted application and can crash the Node.js process via a JavaScript heap out of memory error, resulting in high availability impact without affecting confidentiality or integrity.

The vulnerability has been patched in SVGO versions 2.8.1, 3.3.3, and 4.0.1. Additional details on the issue and remediation are available in the GitHub security advisory at https://github.com/svg/svgo/security/advisories/GHSA-xpqw-6gx7-v673.

OWASP Top 10 for Web (2025)

A02:2025 Security Misconfiguration

EU & UK References

Vulnerability Data

SVGO, short for SVG Optimizer, is a Node.js library and command-line application for optimizing SVG files. From version 2.1.0 to before version 2.8.1, from version 3.0.0 to before version 3.3.3, and before version 4.0.1, SVGO accepts XML with custom entities,…

more

without guards against entity expansion or recursion. This can result in a small XML file (811 bytes) stalling the application and even crashing the Node.js process with JavaScript heap out of memory. This issue has been patched in versions 2.8.1, 3.3.3, and 4.0.1.

CWE(s)
CWE-776

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
attack.mitre.org →
T1499.003 Application Exhaustion Flood Impact
Adversaries may target resource intensive features of applications to cause a denial of service (DoS), denying availability to those applications.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-3415Shared CWE-776
CVE-2025-0617Shared CWE-776
CVE-2024-28982Shared CWE-776
CVE-2026-31248Shared CWE-776
CVE-2024-43398Shared CWE-776
CVE-2026-14979Shared CWE-776
CVE-2026-45771Shared CWE-776
CVE-2023-41635Shared CWE-776
CVE-2024-27141Shared CWE-776
CVE-2024-27142Shared CWE-776

Affected Assets

svgo
svgo
2.1.0 — 2.8.1 · 3.0.0 — 3.3.3 · 4.0.0 — 4.0.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

CM-6 Configuration Settings good match

Secure configuration settings can disable DTD processing or cap entity expansion in XML parsers.

SI-10 Information Input Validation good match

Input validation can enforce limits on XML entity expansion and recursion depth before parsing occurs.

CM-7 Least Functionality partial match

Least-functionality configuration can prohibit unsafe DTD features or external entity resolution.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 full match
prevents

Secure SDLC practices directly prevent introduction of improper recursive entity handling in XML code.

PR.PS-01 mostly match
prevents

Hardened configuration baselines can disable or limit DTD entity expansion in XML parsers.

ID.RA-01 partial match
prevents

Identifying and recording vulnerabilities can discover XML entity expansion flaws before exploitation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect and block XML entity-expansion vulnerabilities before deployment.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates input validation and parser hardening that can prevent unbounded entity expansion.

A.8.26 Application security requirements partial match
prevents

Application security requirements can explicitly call for limits on XML entity recursion and DTD processing.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles discourage unsafe parser configurations that enable entity expansion attacks.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly require disabling or restricting recursive entity references in XML parsers.

References