Skip to main content
VulnerabilityPublished Updated

CVE-2026-73650: SVGO removeScripts plugin leaves some executable scripts intact

Affects svgoSource GCVE Database

0

Mentioned vulnerabilities

CVSS 8.2 High : upgrade to 4.0.2 soon.

Data as of 26 Oct 2026, 16:10 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 4.0.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N

What to do

Upgrade svgo to 4.0.2.

Affected software

ProductAffectedFixed in
npmsvgoAffected
  • >=4.0.0 <4.0.2
Fixed in
  • 4.0.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Fixes for this vulnerability are available in SVGO versions 2.8.3, 3.3.4, and 4.0.2. Users should upgrade to at least these versions to ensure complete removal of executable scripts by the removeScripts plugin. If upgrading is not possible, users should consider using dedicated SVG sanitization tools prior to SVGO processing. The removeScripts plugin is disabled by default, so users relying on it for sanitization should verify their configurations. No additional action is required if the plugin is not enabled or if SVGs are trusted.

Description

SVGO's removeScripts plugin, which is disabled by default, fails to remove all executable scripts from SVG files in certain cases. Specifically, it does not remove namespaced or prefixed <script> elements (e.g., <svg:script>) and matches JavaScript URIs case-sensitively instead of case-insensitively. This can leave executable scripts intact, potentially enabling cross-site scripting (XSS) if untrusted SVGs are processed with this plugin and served to users. SVGO patched these issues in versions 3.3.4 and 4.0.2. Users relying on this plugin for sanitization should upgrade or use dedicated SVG sanitization tools.

References

Community reviews

Loading reviews…