CVE-2026-73650
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…
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.24%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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.
- CVSS 3.1
- 8.2 HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
- EPSS
- 0.24% probability · 16th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-79, CWE-184
- Source
- security-advisories@github.com
References
- https://github.com/svg/svgo/commit/628e3bc7336625a30365d0a9b60185307d852466
- https://github.com/svg/svgo/commit/72a23886b4698b27624b936f3a15a80afd36d75f
- https://github.com/svg/svgo/commit/f529cfccc6c154d6f6eabe276ec637a8c5db6763
- https://github.com/svg/svgo/releases/tag/v2.8.3
- https://github.com/svg/svgo/releases/tag/v3.3.4
- https://github.com/svg/svgo/releases/tag/v4.0.2
- https://github.com/svg/svgo/security/advisories/GHSA-2p49-hgcm-8545
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.