Secuno
ENNL
Book demo

CVE-2026-29074

Svgo vulnerability

7.5 HIGHPublic exploitEPSS 0.97%
  1. Published6 Mar 2026

Description

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.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredNone
User interactionNone
ScopeUnchanged
ConfidentialityNone
IntegrityNone
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

Svgo≥ 2.1.0 < 2.8.1 · ≥ 3.0.0 < 3.3.3 · ≥ 4.0.0 < 4.0.1

Remediation

Fixed in
Svgo≥ 2.8.1

References

and 19 more references

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-34158.7
The XML and schema validation functionalities within the SchemaValidator Mediator…
CVE-2019-191449.8
XML External Entity Injection vulnerability in Quantum DXi6702 2.3.0.3 (11449-53631…

Frequently asked

Is CVE-2026-29074 being actively exploited?

CVE-2026-29074 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.97%.

How severe is CVE-2026-29074?

CVE-2026-29074 has a CVSS 3.1 base score of 7.5, rated high. EPSS estimates a 0.97% probability of exploitation.

Which products are affected by CVE-2026-29074?

Affected products include Svgo.

How do I fix CVE-2026-29074?

Upgrade affected software to a fixed version, for example Svgo 2.8.1 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-29074 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.