VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

react-svg: vulnerability history, versions and safety

react-svg is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 0 release, first recorded in May 2019. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all react-svg vulnerabilities

Vulert verdict on react-svg 19.2.3 i

Updated on 22 Oct 2026

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

Package health score 75/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release 19.2.3 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 31 May 2019 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 9 packages i
  • Stars 881 i
  • OpenSSF scorecard 3/10 i
  • Last release this month 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 react-svg, 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
19.2.3 21 Oct 2026 none MIT — Details →
19.2.2 19 Oct 2026 none MIT — Details →
19.2.1 12 Oct 2026 none MIT — Details →
19.2.0 05 Oct 2026 none MIT — Details →
19.1.6 28 Sep 2026 none MIT — Details →
19.1.5 31 Aug 2026 none MIT — Details →
19.1.4 10 Aug 2026 none MIT — Details →
19.1.3 08 Aug 2026 none MIT — Details →
19.1.2 07 Aug 2026 none MIT — Details →
19.1.1 06 Aug 2026 none MIT — Details →
19.1.0 06 Aug 2026 none MIT — Details →
19.0.0 03 Aug 2026 none MIT — Details →
18.0.2 03 Aug 2026 none MIT — Details →
18.0.1 30 Jul 2026 none MIT — Details →
18.0.0 30 Jul 2026 none MIT — Details →
17.2.5 28 Jul 2026 none MIT — Details →
17.2.4 09 Mar 2026 none MIT — Details →
17.2.3 02 Mar 2026 none MIT — Details →
17.2.2 23 Feb 2026 none MIT — Details →
17.2.1 20 Feb 2026 none MIT — Details →
17.2.0 17 Feb 2026 none MIT — Details →
17.1.1 16 Feb 2026 none MIT — Details →
17.1.0 15 Feb 2026 none MIT — Details →
17.0.4 14 Feb 2026 none MIT — Details →
17.0.3 14 Feb 2026 none MIT — Details →
17.0.2 14 Feb 2026 none MIT — Details →
17.0.1 14 Feb 2026 none MIT — Details →
17.0.0 13 Feb 2026 none MIT — Details →
16.4.2 09 Feb 2026 none MIT — Details →
16.4.1 02 Feb 2026 none MIT — Details →
16.4.0 25 Jan 2026 none MIT — Details →
16.3.1 24 Jan 2026 none MIT — Details →
16.3.0 26 Jan 2025 none MIT — Details →
16.2.0 19 Nov 2024 none MIT — Details →
16.1.34 27 Mar 2024 none MIT — Details →
16.1.33 03 Feb 2024 none MIT — Details →
16.1.32 15 Dec 2023 none MIT — Details →
16.1.31 21 Nov 2023 none MIT — Details →
16.1.30 12 Nov 2023 none MIT — Details →
16.1.29 13 Oct 2023 none MIT — Details →
16.1.28 07 Oct 2023 none MIT — Details →
16.1.27 29 Sep 2023 none MIT — Details →
16.1.26 26 Sep 2023 none MIT — Details →
16.1.25 16 Sep 2023 none MIT — Details →
16.1.24 09 Sep 2023 none MIT — Details →
16.1.23 01 Sep 2023 none MIT — Details →
16.1.22 18 Aug 2023 none MIT — Details →
16.1.21 11 Aug 2023 none MIT — Details →
16.1.20 05 Aug 2023 none MIT — Details →
16.1.19 20 Jul 2023 none MIT — Details →
16.1.18 30 Jun 2023 none MIT — Details →
16.1.17 18 Jun 2023 none MIT — Details →
16.1.16 10 Jun 2023 none MIT — Details →
16.1.15 02 Jun 2023 none MIT — Details →
16.1.14 26 May 2023 none MIT — Details →
16.1.13 20 May 2023 none MIT — Details →
16.1.12 12 May 2023 none MIT — Details →
16.1.11 05 May 2023 none MIT — Details →
16.1.10 29 Apr 2023 none MIT — Details →
16.1.9 24 Apr 2023 none MIT — Details →
16.1.8 17 Apr 2023 none MIT — Details →
16.1.7 27 Mar 2023 none MIT — Details →
16.1.6 10 Mar 2023 none MIT — Details →
16.1.5 03 Mar 2023 none MIT — Details →
16.1.4 24 Feb 2023 none MIT — Details →
16.1.2 17 Feb 2023 none MIT — Details →
16.1.1 12 Feb 2023 none MIT — Details →
16.1.0 04 Feb 2023 none MIT — Details →
16.0.0 23 Jan 2023 none MIT — Details →
15.1.21 16 Jan 2023 none MIT — Details →
15.1.20 15 Jan 2023 none MIT — Details →
15.1.19 13 Jan 2023 none MIT — Details →
15.1.18 06 Jan 2023 none MIT — Details →
15.1.17 23 Dec 2022 none MIT — Details →
15.1.16 18 Dec 2022 none MIT — Details →
15.1.15 10 Dec 2022 none MIT — Details →
15.1.14 27 Nov 2022 none MIT — Details →
15.1.13 19 Nov 2022 none MIT — Details →
15.1.12 11 Nov 2022 none MIT — Details →
15.1.11 29 Oct 2022 none MIT — Details →
15.1.10 09 Oct 2022 none MIT — Details →
15.1.9 18 Sep 2022 none MIT — Details →
15.1.8 09 Sep 2022 none MIT — Details →
15.1.7 22 Aug 2022 none MIT — Details →
15.1.6 14 Aug 2022 none MIT — Details →
15.1.5 07 Aug 2022 none MIT — Details →
15.1.4 29 Jul 2022 none MIT — Details →
15.1.3 15 Jul 2022 none MIT — Details →
15.1.2 08 Jul 2022 none MIT — Details →
15.1.1 02 Jul 2022 none MIT — Details →
15.1.0 28 Jun 2022 none MIT — Details →
15.0.4 18 Jun 2022 none MIT — Details →
15.0.3 10 Jun 2022 none MIT — Details →
15.0.2 03 Jun 2022 none MIT — Details →
15.0.1 03 May 2022 none MIT — Details →
15.0.0 01 May 2022 none MIT — Details →
14.1.19 22 Apr 2022 none MIT — Details →
14.1.18 08 Apr 2022 none MIT — Details →
14.1.17 01 Apr 2022 none MIT — Details →
14.1.16 25 Mar 2022 none MIT — Details →
14.1.15 21 Mar 2022 none — — Details →
14.1.14 11 Mar 2022 none — — Details →
14.1.13 08 Mar 2022 none — — Details →
14.1.12 18 Feb 2022 none — — Details →
14.1.11 11 Feb 2022 none — — Details →
14.1.10 04 Feb 2022 none — — Details →
14.1.9 21 Jan 2022 none — — Details →
14.1.8 16 Jan 2022 none — — Details →
14.1.7 08 Jan 2022 none — — Details →
14.1.6 24 Dec 2021 none — — Details →
14.1.5 17 Dec 2021 none — — Details →
14.1.4 03 Dec 2021 none — — Details →
14.1.3 20 Nov 2021 none — — Details →
14.1.2 12 Nov 2021 none — — Details →
14.1.1 05 Nov 2021 none — — Details →
14.1.0 01 Nov 2021 none — — Details →
14.0.17 22 Oct 2021 none — — Details →
14.0.16 15 Oct 2021 none — — Details →
14.0.15 08 Oct 2021 none — — Details →
14.0.14 03 Oct 2021 none — — Details →

The newest 120 of 399 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1

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

03 Vulnerabilities

Recorded vulnerabilities for react-svg

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Cross-Site Scripting Vulnerability in react-svg N/A high 2.2.18 31 May 2019

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 react-svg

Is react-svg safe to use?

Vulert records 1 vulnerabilities for react-svg in npm: 0 critical, 1 high, 0 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 react-svg's Vulert package health score?

Vulert scores react-svg 75/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 react-svg affected?

No. 19.2.3, 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.

How many vulnerabilities does react-svg have?

1 vulnerability is recorded for react-svg in the npm ecosystem: 0 critical, 1 high, 0 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 react-svg vulnerabilities disclosed?

0 vulnerabilities were recorded for react-svg in the last 12 months, and the oldest entry in this database dates to 31 May 2019. 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 react-svg 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 react-svg for upcoming vulnerabilities?

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