VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

svgo: vulnerability history, versions and safety

svgo is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 33 releases, from Mar 2026 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H3 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 08 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all svgo vulnerabilities

Vulert verdict on svgo 4.1.0 i

Updated on 23 Oct 2026

Good news: 4.1.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 83/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

What to do: Stay on 4.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 4.1.0 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 4 in the last year i
  • Latest disclosure 08 Sep 2026 i
  • Highest CVSS 8.2 i
  • With no published fix 0 i
  • Depended on by 8,000 packages i
  • Stars 22,606 i
  • OpenSSF scorecard 7/10 i
  • Last release 1 month ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for svgo, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
4.1.0 24 Aug 2026 none MIT — Details →
2.8.4 24 Aug 2026 none MIT — Details →
3.3.5 24 Aug 2026 none MIT — Details →
2.8.3 11 Jul 2026 H1 M1 MIT Yes Details →
3.3.4 11 Jul 2026 none MIT — Details →
4.0.2 11 Jul 2026 none MIT — Details →
2.8.2 04 Mar 2026 H2 M1 MIT Yes Details →
2.8.1 04 Mar 2026 H2 M1 MIT Yes Details →
3.3.3 04 Mar 2026 none MIT — Details →
4.0.1 04 Mar 2026 none MIT — Details →
4.0.0 21 Jun 2025 none MIT — Details →
4.0.0-rc.5 11 Jun 2025 none MIT — Details →
4.0.0-rc.4 06 May 2025 none MIT — Details →
4.0.0-rc.3 06 May 2025 none MIT — Details →
4.0.0-rc.2 04 May 2025 none MIT — Details →
4.0.0-rc.1 07 Sep 2024 none MIT — Details →
4.0.0-rc.0 09 Jun 2024 none MIT — Details →
3.3.2 09 May 2024 none MIT — Details →
3.3.1 08 May 2024 none MIT — Details →
3.3.0 08 May 2024 none MIT — Details →
3.2.0 02 Jan 2024 none MIT — Details →
3.1.0 11 Dec 2023 none MIT — Details →
3.0.5 30 Nov 2023 none MIT — Details →
3.0.4 18 Nov 2023 none MIT — Details →
3.0.3 08 Nov 2023 none MIT — Details →
3.0.2 18 Nov 2022 none MIT — Details →
3.0.1 11 Nov 2022 none MIT — Details →
3.0.0 23 Oct 2022 none MIT — Details →
2.8.0 02 Nov 2021 H3 M1 MIT Yes Details →
2.7.0 23 Sep 2021 H3 M1 MIT Yes Details →
2.6.1 15 Sep 2021 H3 M1 MIT Yes Details →
2.6.0 13 Sep 2021 H3 M1 MIT Yes Details →
2.5.0 28 Aug 2021 H3 M1 MIT Yes Details →
2.4.0 13 Aug 2021 H3 M1 MIT Yes Details →
2.3.1 26 Jun 2021 H3 M1 MIT Yes Details →
2.3.0 28 Mar 2021 H3 M1 MIT Yes Details →
2.2.2 09 Mar 2021 H3 M1 MIT Yes Details →
2.2.1 06 Mar 2021 H3 M1 MIT Yes Details →
2.2.0 01 Mar 2021 H3 M1 MIT Yes Details →
2.1.0 23 Feb 2021 H3 M1 MIT Yes Details →
2.0.3 20 Feb 2021 H2 M1 MIT Yes Details →
2.0.2 19 Feb 2021 H2 M1 MIT Yes Details →
2.0.1 18 Feb 2021 H2 M1 MIT Yes Details →
2.0.0 17 Feb 2021 H2 M1 MIT Yes Details →
1.3.2 30 Oct 2019 H2 M1 MIT Yes Details →
1.3.1 29 Oct 2019 H2 M1 MIT Yes Details →
1.3.0 14 Jul 2019 H2 M1 MIT Yes Details →
1.2.2 16 Apr 2019 H2 M1 MIT Yes Details →
1.2.1 04 Apr 2019 H2 M1 MIT Yes Details →
1.2.0 24 Feb 2019 H2 M1 MIT Yes Details →
1.1.1 17 Sep 2018 H2 M1 MIT Yes Details →
1.1.0 16 Sep 2018 H2 M1 MIT Yes Details →
1.0.5 26 Feb 2018 H2 M1 MIT Yes Details →
1.0.4 30 Jan 2018 H2 M1 MIT Yes Details →
1.0.3 08 Nov 2017 H2 M1 MIT Yes Details →
1.0.2 03 Nov 2017 H2 M1 MIT Yes Details →
1.0.1 31 Oct 2017 H2 M1 MIT Yes Details →
1.0.0 30 Oct 2017 H2 M1 MIT Yes Details →
0.7.2 29 Jan 2017 none MIT — Details →
0.7.1 27 Sep 2016 none MIT — Details →
0.7.0 25 Aug 2016 none MIT — Details →
0.6.6 25 Apr 2016 none MIT — Details →
0.6.5 25 Apr 2016 none MIT — Details →
0.6.4 05 Apr 2016 none MIT — Details →
0.6.3 20 Mar 2016 none MIT — Details →
0.6.2 08 Mar 2016 none MIT — Details →
0.6.1 21 Nov 2015 none MIT — Details →
0.6.0 08 Nov 2015 none MIT — Details →
0.5.6 13 Aug 2015 none MIT — Details →
0.5.5 05 Aug 2015 none MIT — Details →
0.5.4 05 Aug 2015 none MIT — Details →
0.5.3 21 Jun 2015 none MIT — Details →
0.5.2 24 May 2015 none MIT — Details →
0.5.1 30 Mar 2015 none MIT — Details →
0.5.0 04 Nov 2014 none MIT — Details →
0.4.5 02 Aug 2014 none MIT — Details →
0.4.4 14 Jan 2014 none MIT — Details →
0.4.3 02 Jan 2014 none MIT — Details →
0.4.2 19 Dec 2013 none MIT — Details →
0.4.1 18 Nov 2013 none MIT — Details →
0.4.0 18 Nov 2013 none MIT — Details →
0.3.7 24 Jun 2013 none MIT — Details →
0.3.6 06 Jun 2013 none MIT — Details →
0.3.5 07 May 2013 none MIT — Details →
0.3.4 06 May 2013 none MIT — Details →
0.3.3 05 May 2013 none MIT — Details →
0.3.2 03 May 2013 none MIT — Details →
0.3.1 15 Apr 2013 none MIT — Details →
0.3.0 12 Apr 2013 none MIT — Details →
0.2.4 05 Apr 2013 none MIT — Details →
0.2.3 22 Feb 2013 none MIT — Details →
0.2.2 09 Feb 2013 none MIT — Details →
0.2.1 18 Jan 2013 none MIT — Details →
0.2.0 23 Dec 2012 none MIT — Details →
0.1.9-1 21 Dec 2012 none MIT — Details →
0.1.9 17 Dec 2012 none MIT — Details →
0.1.8 11 Dec 2012 none MIT — Details →
0.1.7 08 Dec 2012 none MIT — Details →
0.1.6 07 Dec 2012 none MIT — Details →
0.1.5 06 Dec 2012 none MIT — Details →
0.1.4 06 Dec 2012 none — — Details →
0.1.3 30 Nov 2012 none — — Details →
0.1.2 23 Nov 2012 none — — Details →
0.1.1 23 Nov 2012 none — — Details →
0.1.0 22 Nov 2012 none — — Details →
0.0.9-1 06 Nov 2012 none — — Details →
0.0.9 28 Oct 2012 none — — Details →
0.0.8 20 Oct 2012 none — — Details →
0.0.7-1 15 Oct 2012 none — — Details →
0.0.7 14 Oct 2012 none — — Details →
0.0.6 04 Oct 2012 none — — Details →
0.0.5-1 03 Oct 2012 none — — Details →
0.0.5 03 Oct 2012 none — — Details →
0.0.4 29 Sep 2012 none — — Details →
0.0.3 29 Sep 2012 none — — Details →
0.0.2 28 Sep 2012 none — — Details →
0.0.1-3 28 Sep 2012 none — — Details →
0.0.1-2 27 Sep 2012 none — — Details →
0.0.1 27 Sep 2012 none — — Details →

All 119 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 4 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for svgo

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
SVGO Vulnerability: Incomplete Script Removal Leading to Potential XSS Attacks 8.2 high 2.8.3 21 Jul 2026
CVE-2026-84370: SVGO Vulnerability in removeScripts Plugin Allows Executable Links 8.2 high 2.8.4 08 Sep 2026
CVE-2026-29074: SVGO DoS Vulnerability via Entity Expansion in DOCTYPE 7.5 high 2.8.1 04 Mar 2026
CVE-2026-84369: SVGO Incomplete Sanitization of Executable HTML in SVG foreignObject Elements 6.1 medium 2.8.4 08 Sep 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About svgo

Is svgo safe to use?

Vulert records 4 vulnerabilities for svgo in npm: 0 critical, 3 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is svgo's Vulert package health score?

Vulert scores svgo 83/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of svgo affected?

No. 4.1.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of svgo should I use?

4.1.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does svgo have?

4 vulnerabilities are recorded for svgo in the npm ecosystem: 0 critical, 3 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new svgo vulnerabilities disclosed?

4 vulnerabilities were recorded for svgo in the last 12 months, and the oldest entry in this database dates to 04 Mar 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of svgo are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor svgo for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the svgo version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.