LiveActive security incident?Get immediate response
CVE Record

CVE-2026-29074: SVGO: DoS through entity expansion in DOCTYPE (Billion Laughs)

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, 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.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-29074 is a denial-of-service issue in SVGO, a Node.js SVG optimization library and CLI. Malformed SVG/XML using recursive custom entities can stall the application or crash Node.js from memory exhaustion. This affects availability, not confidentiality or integrity. Patched SVGO versions are available.

Executive priority

Prioritize remediation for internet-facing or multi-tenant services that process uploaded SVG files. This is an availability risk with published fixes and low implementation complexity. Environments using SVGO only on trusted internal assets can schedule normal patching after confirming exposure.

Technical view

SVGO versions 2.1.0 through before 2.8.1, 3.0.0 through before 3.3.3, and 4.0.0 accept XML custom entities without adequate expansion or recursion guards. The advisory maps this to CWE-776 and CVSS 7.5, with network, low-complexity, unauthenticated availability impact.

Likely exposure

Exposure is most relevant where SVGO processes SVG files from users, partners, build pipelines, CMS workflows, or automated asset tooling. Direct CLI-only use on trusted local files is lower risk. Transitive npm dependencies may also embed vulnerable SVGO versions.

Exploitation context

The provided sources do not indicate known active exploitation, and the CVE is not marked KEV. Abuse requires getting SVGO to process a crafted SVG/XML document. Successful exploitation can hang optimization jobs or terminate the Node.js process through heap exhaustion.

Researcher notes

The core issue is unbounded XML entity expansion/recursion in SVGO parsing behavior. Sources state a very small XML file can stall the application or crash Node.js with heap out-of-memory. Public sources provided do not include evidence of data exposure, privilege escalation, or confirmed exploitation in the wild.

Mitigation direction

  • Upgrade SVGO to 2.8.1, 3.3.3, 4.0.1, or later as appropriate.
  • Review Red Hat advisories if consuming SVGO through Red Hat-distributed packages.
  • Restrict untrusted SVG processing until vulnerable instances are upgraded.
  • Add resource limits and monitoring around SVG optimization services.

Validation and detection

  • Inventory direct and transitive SVGO versions in application dependencies.
  • Confirm no deployed package uses affected SVGO version ranges.
  • Check image-processing, CMS, CI, and asset-build workflows for SVG uploads.
  • Verify Red Hat package status against applicable RHSA advisories.
  • Monitor affected services for crashes or memory exhaustion during SVG processing.
Prepared
Confidence
high
Sources
5

Public sources used

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-776: 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 lookup
cve · low confidence lookup

CVE-2026-29074 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
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

Official CVE source material

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.

2CVSS vectors
5Timeline events
2ADP providers
29Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

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.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6GitHub_M
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2026-29074Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Reported to Red Hat.

  3. ADP timelineredhat-SADP

    Made public.

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPsvgo: SVGO: Denial of Service via XML entity expansion
other:Red Hat severity ratingcvssV3_1
  • 2026-03-06T00:00:00.000Z: Reported to Red Hat.
  • 2026-03-06T07:23:05.716Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
svgsvgo>= 2.1.0, < 2.8.1, >= 3.0.0, < 3.3.3, = 4.0.0Listed
Weakness

CWE details

CWE-776

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-776 · source CWE mapping

Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')

Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs