CVE-2026-29074: SVGO, short for SVG Optimizer, is a Node.js library and command-line application for optimizing SVG files

Q: How do I fix CVE-2026-29074?

svgo: upgrade to 2.8.1, 3.3.3, 4.0.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-29074 being exploited?

CVE-2026-29074 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-29074 affect?

CVE-2026-29074 affects svgo. Severity is high (CVSS 7.5). 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 wi

Q: How urgent is CVE-2026-29074?

Priority 49/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

HIGH 7.5REMOTEUPGRADE

CVE-2026-29074 is a high-severity flaw (CVSS 7.5) affecting svgo. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.6% (top 50%)
CISA exploited list	No
Weakness	CWE-776
Published	2026-03-06
Last modified	2026-09-10

Publisher (CNA): GitHub, Inc. · Vendor: svgo

Last updated 2026-09-10 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-06 08:16 UTCPublished CVE record published
2026-09-10 13:18 UTCUpdated Record last modified

svgo svgo UPGRADE

Affected: >= 2.1.0 and < 2.8.1 · >= 3.0.0 and < 3.3.3 · >= 4.0.0 and < 4.0.1

Fixed in: 2.8.1, 3.3.3, 4.0.1

Safe to downgrade to: a release before 2.1.0

1. Check installed version

npm ls svgo

2. UPGRADE to 2.8.1

npm install svgo@">=2.8.1"

3. If no update is available yet, DOWNGRADE to a release before 2.1.0

npm view svgo versions npm install svgo@"<2.1.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-29074?

svgo: upgrade to 2.8.1, 3.3.3, 4.0.1. Exact commands for each OS are on this page.

Is CVE-2026-29074 being exploited?

CVE-2026-29074 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-29074 affect?

CVE-2026-29074 affects svgo. Severity is high (CVSS 7.5). 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 wi

How urgent is CVE-2026-29074?

Priority 49/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Node.js vulnerabilities

References

← Back to latest CVEs