SVGO, short for SVG Optimizer, is a Node.js library and command-line application for optimizing SVG files. From version 1.0.0 until versions 2.8.4, 3.3.5, and 4.1.0, the opt-in removeScripts plugin, named removeScriptElement in versions 2 and 3, incompletely filters executable links in plugins/removeScripts.js and lib/svgo/tools.js. The plugin does not recognize namespace-prefixed SVG anchor elements such as svg:a with href or namespaced *:href values, and it does not remove ASCII tab, line-feed, or carriage-return characters before checking URL schemes. Browsers remove those characters before parsing a scheme, allowing an executable link to pass the plugin's check. When an application processes attacker-controlled SVG input and serves the result in an active browser context, a victim who activates the surviving link can execute script in the SVG's origin, expose data, modify content, or perform actions as the victim. This issue is fixed in versions 2.8.4, 3.3.5, and 4.1.0.
CVE-2026-84370
This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.2
- EG Score
- 8.2(medium)
- EG Risk
- 37(Track)EG Risk 37/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity82% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 27%
- KEV
- Not listed
Published
September 1, 2026
Last Modified
September 9, 2026
Advisory Details (10)
Auto-updated Sep 1, 2026v4.1.0
Patch available: svg/svgo v4.1.0
https://github.com/svg/svgo/releases/tag/v4.1.0v3.3.5
Patch available: svg/svgo v3.3.5
https://github.com/svg/svgo/releases/tag/v3.3.5v2.8.4
Patch available: svg/svgo v2.8.4
https://github.com/svg/svgo/releases/tag/v2.8.4commit 994a9f00d79d (svg/svgo)
Patch available: svg/svgo v3.3.5 (contains commit 994a9f00d79d)
https://github.com/svg/svgo/commit/994a9f00d79ddec68ce19a1ce9eb8ca08d747e4fcommit 3db3ef33e409 (svg/svgo)
Patch available: svg/svgo v4.1.0 (contains commit 3db3ef33e409)
https://github.com/svg/svgo/commit/3db3ef33e409a0bc0fdaf255e46c908b00e93bc2commit 0557385564a5 (svg/svgo)
Patch available: svg/svgo v2.8.4 (contains commit 0557385564a5)
https://github.com/svg/svgo/commit/0557385564a5c6c11d76cd934a6cff94451e532cfix(removeScriptElement): backport security hardening to v2
Patch available: svg/svgo v2.8.4 (PR #2272 merged 2026-08-24)
https://github.com/svg/svgo/pull/2272fix(removeScriptElement): backport security hardening to v3
Patch available: svg/svgo v3.3.5 (PR #2269 merged 2026-08-24)
https://github.com/svg/svgo/pull/2269fix(removeScripts): handle anchor URL bypasses
Patch available: svg/svgo v4.1.0 (PR #2268 merged 2026-08-24)
https://github.com/svg/svgo/pull/2268removeScripts allows executable links through namespace and control-character bypasses · Advisory · svg/svgo · GitHub
https://github.com/svg/svgo/security/advisories/GHSA-w27v-7q3p-w38rVendor Advisories for CVE-2026-84370(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| svgo | — | 4.1.0 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 34× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-18 21:58 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-17 20:40 UTCEG score recompute
- 2026-09-17 19:32 UTCEPSS rescore
- 2026-09-16 18:38 UTCEG score recompute
- 2026-09-16 14:09 UTCEPSS rescore
- 2026-09-16 05:33 UTCEG score recompute
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 04:16 UTCEG score recompute
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 02:58 UTCEG score recompute
- 2026-09-13 01:42 UTCEG score recompute
- 2026-09-12 00:25 UTCEG score recompute
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 11:46 UTCEG score recompute
- 2026-09-10 09:49 UTCEG score recompute
- 2026-09-08 23:18 UTCEG score recompute
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-07 20:01 UTCEG score recompute
- 2026-09-06 18:42 UTCEG score recompute
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-05 17:25 UTCEG score recompute
- 2026-09-05 15:31 UTCEPSS rescore
Show 9 moreShow fewer
- 2026-09-04 16:03 UTCEG score recompute
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-04 03:23 UTCEG score recompute
- 2026-09-04 02:34 UTCEG score recompute
- 2026-09-02 22:43 UTCEG score recompute
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-01 21:26 UTCEG score recompute
- 2026-09-01 20:53 UTCEG score recompute
- 2026-09-01 20:52 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-84370?
When was CVE-2026-84370 disclosed?
Is CVE-2026-84370 actively exploited?
What is the CVSS score of CVE-2026-84370?
How do I remediate CVE-2026-84370?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-84370
Is Your Infrastructure Affected by CVE-2026-84370?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.