CVE-2026-73650 json
SVGO: removeScripts plugin leaves some executable scripts intact
published 2026-07-21 3 mo ago modified 2026-09-18 51 d ago also GHSA-2p49-hgcm-8545 , EUVD-2026-58193
- cvss
- 8.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 37%
- public exploits
- 0
- none known
Summary
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.3, 3.3.4, and 4.0.2, the removeScripts plugin, named removeScriptElement in versions 1 through 3, can leave executable content in optimized SVGs because it does not remove namespaced or prefixed script elements such as <svg:script> and, in versions 3 and 4, matches JavaScript URIs case sensitively. Applications that process untrusted SVG input with this plugin enabled and serve the result can allow scripts to execute when another user opens the SVG, exposing local storage or cookies. This issue is fixed in versions 2.8.3, 3.3.4, and 4.0.2.
Patch / fix
- npm svgo 2.8.3, 3.3.4, 4.0.2
- node-svgo Debian 14 3.3.5+ds-1
debian advisories DEBIAN-CVE-2026-73650
- velociraptor openSUSE Tumbleweed 0.76.7.0.git145.b60ef1146-1.1
- agama-web-ui openSUSE Tumbleweed 24+0.a836cced5-52.1
opensuse advisories openSUSE-SU-2026:12070-1openSUSE-SU-2026:11680-1
- github.com/svg/svgo@628e3bc commit
- github.com/svg/svgo@72a2388 commit
- github.com/svg/svgo@f529cfc commit
- github.com/svg/svgo/releases/tag/v2.8.3 release
- github.com/svg/svgo/releases/tag/v3.3.4 release
- github.com/svg/svgo/releases/tag/v4.0.2 release
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 mo ago
Exploit prediction
0.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N |
| GitHub | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | svgo | >=1.0.0, <2.8.3 >=3.0.0, <3.3.4 >=4.0.0, <4.0.2 |
2.8.3 3.3.4 4.0.2 |
Affected products
- svg svgo
Classification
References
-
github.com
/svg/svgo/commit/628e3bc7336625a30365d0a9b60185307d852466
web
-
github.com
/svg/svgo/commit/72a23886b4698b27624b936f3a15a80afd36d75f
web
-
github.com
/svg/svgo/commit/f529cfccc6c154d6f6eabe276ec637a8c5db6763
web
-
github.com
/svg/svgo/security/advisories/GHSA-2p49-hgcm-8545
web
-
github.com
/svg/svgo/releases/tag/v2.8.3
web
-
github.com
/svg/svgo/releases/tag/v3.3.4
web
-
github.com
/svg/svgo/releases/tag/v4.0.2
web
-
github.com
/svg/svgo
package
Sources
- CVE List CVE-2026-73650
- GitHub Advisory GHSA-2p49-hgcm-8545
- NVD CVE-2026-73650
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.