CVE-2026-84369 SVGO: removeScripts incompletely sanitizes executable HTML in SVG foreignObject elements
Attackers can execute arbitrary JavaScript in victim browsers via unsanitized HTML in SVG foreignObject elements when using the opt-in removeScripts plugin.
- 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
What is CVE-2026-84369?
CVE-2026-84369 is a medium-severity cross-site scripting vulnerability in svgo, published on 1 Sep 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.4, 3.3.5, and 4.1.0, the opt-in removeScripts plugin, named removeScriptElement in versions 2 and 3 and implemented in plugins/removeScripts.js, removes SVG and XHTML script elements but does not inspect executable HTML content inside SVG foreignObject elements. Event-handler attributes such as onload and onbeforetoggle, srcdoc documents, and executable URLs in the action, data, formaction, href, and src attributes can remain in attacker-controlled SVG input. When an application uses the plugin as its only protection and serves the optimized SVG in an active browser context, the payload can execute script in the viewer's origin, expose data, modify content, or perform actions as the victim. This issue is fixed in versions 2.8.4, 3.3.5, and 4.1.0.
Weakness: CWE-79
Which versions are affected by CVE-2026-84369?
6 open source packages ship an affected version, including svgo.
| Package | Affected | Fixed in |
|---|---|---|
svgo npm | From 1.0.0 | 2.8.4 |
svgo npm | From 1.0.0 | 2.8.4 |
svgo npm | From 3.0.0 | 3.3.5 |
svgo npm | From 3.0.0 | 3.3.5 |
svgo npm | From 4.0.0 | 4.1.0 |
svgo npm | From 4.0.0 | 4.1.0 |
How do I fix CVE-2026-84369?
Upgrade svgo to a fixed version for your release line: 2.8.4, 3.3.5 or 4.1.0.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-84369 being exploited?
There is no known exploitation of CVE-2026-84369 in the wild and no public exploit code.
Sources
Also known as CLSA-2026-1790520171, DEBIAN-CVE-2026-84369, GHSA-4vpr-x523-8j87.