Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.2amended

SVGO removeScripts plugin leaves some executable scripts intact

CVE-2026-73650GHSA-2p49-hgcm-8545

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (svgo 4.0.2, 3.3.4, 2.8.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm svgo

    Affected
    >= 1.0.0, < 2.8.3>= 3.0.0, < 3.3.4>= 4.0.0, < 4.0.2
    Fixed in
    4.0.2, 3.3.4, 2.8.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N
EPSS
  • CVE-2026-73650: 0.43% estimated exploitation activity in the next 30 days; percentile 37.80 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary SVGO's removeScripts plugin (disabled by default) removes scripts from the SVG, however executable scripts were left intact in some cases. If a consumer relied on this plugin for sanitization and served them to users, these SVGs could open up doors to XSS. Details SVGO has a plugin for removing scripts from an SVG, which removes: - <script elements - JavaScript URIs (v4 and v3 only) - on… event handlers (v4 and v3 only) While SVGO is not a sanitization library, SVGO continues to maintain the plugin for those already using it for this purpose. However, there were two problems: - SVGO did not check namespaced/prefixed script elements, for example if one declared an explicit prefix for the SVG namespace ( <svg:script) instead of using the default namespace ( <script), the <svg:script tag would be left intact. - SVGO case sensitively matched JavaScript URIs, but it should've been case-insensitive. Proof of Concept Impact If you run SVGO on untrusted input (e.g., user uploads to a…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-2p49-hgcm-8545

  2. Revision 1 · created ·

    Published from osv record GHSA-2p49-hgcm-8545

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-73650

Advisory: SVGO removeScripts plugin leaves some executable scripts intact
IDs: CVE-2026-73650, GHSA-2p49-hgcm-8545
Record: https://patchnext.com/advisories/cve-2026-73650 (revision 2, source checked 26 Oct 2026, 13:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: svgo 4.0.2, 3.3.4, 2.8.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm svgo: affected >= 1.0.0, < 2.8.3; >= 3.0.0, < 3.3.4; >= 4.0.0, < 4.0.2; fixed in 4.0.2, 3.3.4, 2.8.3

## Suggested inspection (read-only)
- `npm ls svgo --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on svgo.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-2p49-hgcm-8545 (OSV record GHSA-2p49-hgcm-8545 lists affected ranges: npm svgo >=1.0.0 =3.0.0 =4.0.0 <4.0.2 (fixed))
- Verified: https://github.com/advisories/GHSA-2p49-hgcm-8545 (GitHub-reviewed advisory GHSA-2p49-hgcm-8545 lists affected ranges: npm svgo >=1.0.0 =3.0.0 =4.0.0 <4.0.2)

Commands are suggestions: review each one before running it.

Loading voting…