chore(deps): update dependency svgo@>=3.0.0 <3.3.3 to v3.3.5 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
svgo@>=3.0.0 <3.3.3 (source)	[3.3.3 → 3.3.5](https://renovatebot.com/diffs/npm/svgo@>=3.0.0 <3.3.3/3.3.3/3.3.5)

---

SVGO removeScripts plugin leaves some executable scripts intact

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

More information

Details

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

import { optimize } from 'svgo';

/** Presume that this string was obtained in some other way, such as network. */
const original = `
  <svg xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" xmlns:uwu="http://www.w3.org/1999/xlink" viewBox="0 0 100 100" version="1.1">
    <a uwu:href="JavaScript:(() =&gt; { alert(document.cookie) })();"><text y="30">uwu</text></a>
    <svg:script>
      alert(document.cookie);
    </svg:script>
  </svg>
`;

optimize(original, {
  plugins: ['removeScripts']
});
// Did not remove <svg:script> or uwu:href="JavaScript:…—still executed by browsers.

Impact

If you run SVGO on untrusted input (e.g., user uploads to a web application) and you depended on removeScripts, then some scripts may still be present. If that SVG was then opened directly by another user on the same domain, it could invoke scripts that could read local storage or cookies.

This may affect you if you have enabled one of the following:

SVGO Version	Plugin Name
v4	removeScripts
v3	removeScriptElement
v2	removeScriptElement
v1	removeScriptElement

It's unlikely to impact users who just use SVGO locally on their own SVGs or in build pipelines.

Patches

>= 3.0.0, <= 4.0.1

SVGO patched v4.0.2 and v3.3.4. Just upgrade the dependency using your preferred package manager! For example:

yarn up svgo

##### or if SVGO is a nested dependency
yarn up -R svgo

The proposed fix is to improve our namespace-aware handling to explicitly act on the default namespace, SVG namespace, and XHTML namespace only. This handles all scripts that are executed by browsers, but will leave intact custom prefixes that happen to have an element called <*:script> which clients shouldn't treat as executable.

>= 2.0.0, <= 2.8.2

SVGO patched v2.8.3, however SVGO v2 explicitly only implements and documents that it will remove <script> elements and nothing more. It has the namespace aware handling for tags like <svg:script> or <xhtml:script>, but has not been updated to remove JavaScript URIs or event handlers like >= v3. If this is something you need, please upgrade to v4 or v3, or reach for one of the documented workarounds at the end.

>= 1.0.0, <= 1.3.2

SVGO v1 has been deprecated for a while now and won't be patched. Please upgrade to a more recent version! If something is preventing you from doing so, please reach out! We're happy to expand our migration guides or support you if you're having trouble.

Workarounds

If your motivation for enabling the plugin is SVG sanitization, consider reaching for a dedicated SVG sanitization tool and invoke it before passing the SVG to SVGO.

Severity

• CVSS Score: 8.2 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N

References

• https://github.com/svg/svgo/security/advisories/GHSA-2p49-hgcm-8545
• 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
• 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

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

SVGO: removeScripts incompletely sanitizes executable HTML in SVG foreignObject elements

CVE-2026-84369 / GHSA-4vpr-x523-8j87

More information

Details

Summary

SVGO's opt-in removeScripts plugin did not inspect executable HTML content inside SVG <foreignObject> elements. Applications that used this plugin as their only protection for untrusted SVG input could produce SVGs containing active HTML and expose users to cross-site scripting (XSS).

SVGO is an optimizer rather than a comprehensive sanitization library, but removeScripts is maintained for consumers that already rely on it to remove common script execution paths.

Details

Although the plugin removed SVG and XHTML <script> elements, it left other HTML execution paths inside <foreignObject> unchanged. These included:

• event-handler attributes such as onload and onbeforetoggle;
• srcdoc documents, including on <iframe> elements;
• executable URLs in HTML attributes such as action, data, formaction, href, and src.

An attacker could place one of these payloads in an SVG. If an application optimized the untrusted SVG with removeScripts and then served the result in an active browser context, the payload could execute in the viewer's origin.

Impact

Successful exploitation could allow script execution in the context where the optimized SVG is rendered. Depending on the embedding and origin configuration, this could expose cookies or local storage, modify content, or perform actions as the victim.

The plugin is opt-in, so consumers that do not enable removeScripts are not relying on the affected behavior. Typical local optimization of trusted SVG files is not affected.

Patches

Upgrade to one of the following releases for the maintained release line in use:

Release line	Patched version	Plugin
v2	2.8.4	removeScriptElement
v3	3.3.5	removeScriptElement
v4	4.1.0	removeScripts

The fix preserves visual HTML inside SVG <foreignObject> elements while removing event attributes, srcdoc, and executable URL values from active HTML URL attributes.

SVGO v1 is no longer maintained. Users of v1 should upgrade to a supported release line.

Workarounds

For hostile input, use a dedicated SVG sanitization tool before passing the SVG to SVGO. As defense in depth, applications can reject or remove <foreignObject> content and avoid serving user-controlled SVGs in an active same-origin context.

Severity

• CVSS Score: 6.1 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

References

• https://github.com/svg/svgo/security/advisories/GHSA-4vpr-x523-8j87
• https://nvd.nist.gov/vuln/detail/CVE-2026-84369
• https://github.com/svg/svgo/pull/2264
• https://github.com/svg/svgo/pull/2269
• https://github.com/svg/svgo/pull/2272
• https://github.com/svg/svgo/commit/0557385564a5c6c11d76cd934a6cff94451e532c
• https://github.com/svg/svgo/commit/994a9f00d79ddec68ce19a1ce9eb8ca08d747e4f
• https://github.com/svg/svgo/commit/fd51e474a300417d9361d9302d596b1763146327
• https://github.com/svg/svgo
• https://github.com/svg/svgo/releases/tag/v2.8.4
• https://github.com/svg/svgo/releases/tag/v3.3.5
• https://github.com/svg/svgo/releases/tag/v4.1.0

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

SVGO: removeScripts allows executable links through namespace and control-character bypasses

CVE-2026-84370 / GHSA-w27v-7q3p-w38r

More information

Details

Summary

SVGO's opt-in removeScripts plugin failed to remove some executable links. Namespace-prefixed SVG anchors and URL schemes containing ASCII tabs or newlines could bypass its checks. Applications that used this plugin as their only protection for untrusted SVG input could expose users to cross-site scripting (XSS).

SVGO is an optimizer rather than a comprehensive sanitization library, but removeScripts is maintained for consumers that already rely on it to remove common script execution paths.

Details

Two related bypasses were present:

1. The plugin inspected unprefixed SVG <a> elements but did not recognize namespace-prefixed SVG anchors such as <svg:a> when the prefix was bound to the SVG namespace. Their executable href or namespaced *:href values remained intact.
2. The URL check did not account for ASCII tab, line-feed, or carriage-return characters embedded in a scheme. Browsers remove these characters before parsing the scheme, so values such as java&#​9;script: could remain executable after bypassing the plugin's javascript: check.

Anchors in unrelated custom namespaces are not executable SVG anchors and remain untouched.

Impact

If an application optimized attacker-controlled SVGs with removeScripts and then served the result in an active browser context, a victim could follow a link that executes script in the SVG's origin. Depending on the embedding and origin configuration, this could expose cookies or local storage, modify content, or perform actions as the victim.

The plugin is opt-in, so consumers that do not enable it are not relying on the affected behavior. Typical local optimization of trusted SVG files is not affected.

Patches

Upgrade to one of the following releases for the maintained release line in use:

Release line	Patched version	Plugin
v2	2.8.4	removeScriptElement
v3	3.3.5	removeScriptElement
v4	4.1.0	removeScripts

The fix makes SVG anchor handling namespace-aware and strips ASCII tabs, line feeds, and carriage returns before checking executable URL schemes.

SVGO v1 is no longer maintained. Users of v1 should upgrade to a supported release line.

Workarounds

For hostile input, use a dedicated SVG sanitization tool before passing the SVG to SVGO. Applications can also reject links from untrusted SVG input and avoid serving user-controlled SVGs in an active same-origin context.

References

• v4 fix: https://github.com/svg/svgo/pull/2268
• related executable URL hardening: https://github.com/svg/svgo/pull/2263
• v3 backport: https://github.com/svg/svgo/pull/2269
• v2 backport: https://github.com/svg/svgo/pull/2272
• v4.1.0 release: https://github.com/svg/svgo/releases/tag/v4.1.0
• v3.3.5 release: https://github.com/svg/svgo/releases/tag/v3.3.5
• v2.8.4 release: https://github.com/svg/svgo/releases/tag/v2.8.4

Severity

• CVSS Score: 8.2 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N

References

• https://github.com/svg/svgo/security/advisories/GHSA-w27v-7q3p-w38r
• https://nvd.nist.gov/vuln/detail/CVE-2026-84370
• https://github.com/svg/svgo/pull/2268
• https://github.com/svg/svgo/pull/2269
• https://github.com/svg/svgo/pull/2272
• https://github.com/svg/svgo/commit/0557385564a5c6c11d76cd934a6cff94451e532c
• https://github.com/svg/svgo/commit/3db3ef33e409a0bc0fdaf255e46c908b00e93bc2
• https://github.com/svg/svgo/commit/994a9f00d79ddec68ce19a1ce9eb8ca08d747e4f
• https://github.com/svg/svgo
• https://github.com/svg/svgo/releases/tag/v2.8.4
• https://github.com/svg/svgo/releases/tag/v3.3.5
• https://github.com/svg/svgo/releases/tag/v4.1.0

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

svg/svgo (svgo@>=3.0.0 <3.3.3)

v3.3.5

Compare Source

What's Changed

Security

• Backport the removeScriptElement hardening from SVGO v4 in #​2269:
  • reject executable data: URLs and legacy vbscript: URLs
  • sanitize executable HTML inside <foreignObject> elements
  • handle namespace-prefixed SVG anchors and URL schemes containing ASCII tabs or newlines

This addresses GHSA-4vpr-x523-8j87 and GHSA-w27v-7q3p-w38r for the v3 release line.

Support

SVGO v3 is not officially supported; please consider upgrading to SVGO v4. This security fix has been backported, but there is no commitment to backport more complex changes in the future.

See the migration guide from v3 to v4.

v3.3.4

Compare Source

What's Changed

Security

• removeScriptElement, remove JavaScript URIs case-insensitively and make <script> handling namespace aware. By @​SethFalco

Support

SVGO v3 is not officially supported, please consider upgrading to SVGO v4 instead. We've backported this fix as there are security implications, but there is no commitment to do this for more complex changes in future.

Consider reading our Migration Guide from v3 to v4 which should ease the process.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.