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

> Attackers can inject executable scripts into SVGs processed by SVGO, leading to XSS and data theft when victims view the files.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** CLSA-2026-1784682960, CLSA-2026-1790176195, DEBIAN-CVE-2026-73650, GHSA-2p49-hgcm-8545, ROOT-APP-NPM-CVE-2026-73650, ROOT-APP-NPM-GHSA-2p49-hgcm-8545

## What is CVE-2026-73650?

CVE-2026-73650 is a high-severity cross-site scripting vulnerability in svgo, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-184 (Incomplete List of Disallowed Inputs)

## Which versions are affected by CVE-2026-73650?

6 open source packages ship an affected version, including svgo.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `svgo` | npm | From 1.0.0 | 2.8.3 |
| `svgo` | npm | From 1.0.0 | 2.8.3 |
| `svgo` | npm | From 3.0.0 | 3.3.4 |
| `svgo` | npm | From 3.0.0 | 3.3.4 |
| `svgo` | npm | From 4.0.0 | 4.0.2 |
| `svgo` | npm | From 4.0.0 | 4.0.2 |

## How do I fix CVE-2026-73650?

Upgrade svgo to a fixed version for your release line: 2.8.3, 3.3.4 or 4.0.2.

## Is CVE-2026-73650 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73650 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73650 and fix it if it is affected.

What it is: CVE-2026-73650 is a high-severity cross-site scripting vulnerability in svgo, published on 13 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-73650 exists.

Affected packages and fixed versions:
- svgo (npm): affected from 1.0.0; fixed in 2.8.3
- svgo (npm): affected from 1.0.0; fixed in 2.8.3
- svgo (npm): affected from 3.0.0; fixed in 3.3.4
- svgo (npm): affected from 3.0.0; fixed in 3.3.4
- svgo (npm): affected from 4.0.0; fixed in 4.0.2
- svgo (npm): affected from 4.0.0; fixed in 4.0.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73650/ (Markdown: https://insights.sbomify.com/CVE-2026-73650/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73650
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73650
- OSV: https://osv.dev/vulnerability/CVE-2026-73650

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73650/
Summaries are generated and may contain mistakes; the official description above is the record.