VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

react: vulnerability history, versions and safety

react is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 120 releases, from Sep 2020 to Jun 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 H1 M1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all react vulnerabilities

Vulert verdict on react 19.3.1 i

Updated on 22 Oct 2026

Careful: 19.3.1 was published with malicious code in it, not just a bug. Do not install it.

Package health score 15/100
  • Security Malicious code published
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

The current release contains malicious code, which caps this score.

What to do: Do not resolve 19.3.1 as-is. Check whether you already run an affected release and pin a version the maintainers have re-published. Check what you run: Vulert alerts you when a safe version is published. Monitor it with Vulert →

  • Current release 19.3.1 — affected i
  • Vulnerabilities on record 3 over 3 years · 0 in the last year i
  • Latest disclosure 25 Jun 2024 i
  • Highest CVSS 6.5 i
  • With no published fix 1 i
  • Malicious packages 1 i
  • Depended on by 32,275 packages i
  • Stars 251,401 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, 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
0.0.0-experimental-9ffcb463-20261021 22 Oct 2026 C1 malicious MIT No Details →
19.3.0-canary-9ffcb463-20261021 22 Oct 2026 C1 malicious MIT No Details →
0.0.0-experimental-ab0d927f-20261020 21 Oct 2026 C1 malicious MIT No Details →
19.3.0-canary-ab0d927f-20261020 21 Oct 2026 C1 malicious MIT No Details →
0.0.0-experimental-a6792708-20261019 20 Oct 2026 C1 malicious MIT No Details →
19.3.0-canary-a6792708-20261019 20 Oct 2026 C1 malicious MIT No Details →
0.0.0-experimental-ba39b32a-20261019 19 Oct 2026 C1 malicious MIT No Details →
19.3.0-canary-ba39b32a-20261019 19 Oct 2026 C1 malicious MIT No Details →
0.0.0-experimental-098d2e87-20261015 15 Oct 2026 C1 malicious MIT No Details →
19.3.0-canary-098d2e87-20261015 15 Oct 2026 C1 malicious MIT No Details →
0.0.0-experimental-99c106c4-20261014 14 Oct 2026 C1 malicious MIT No Details →
19.3.0-canary-99c106c4-20261014 14 Oct 2026 C1 malicious MIT No Details →
19.1.10 14 Oct 2026 C1 malicious MIT No Details →
19.2.9 14 Oct 2026 C1 malicious MIT No Details →
19.0.9 14 Oct 2026 C1 malicious MIT No Details →
19.3.1 14 Oct 2026 C1 malicious MIT No Details →
0.0.0-experimental-07dde64d-20261013 13 Oct 2026 C1 malicious MIT No Details →
19.3.0-canary-07dde64d-20261013 13 Oct 2026 C1 malicious MIT No Details →
0.0.0-experimental-9f2e1f88-20261012 12 Oct 2026 C1 malicious MIT No Details →
19.3.0-canary-9f2e1f88-20261012 12 Oct 2026 C1 malicious MIT No Details →
0.0.0-experimental-b618bbb4-20261007 08 Oct 2026 C1 malicious MIT No Details →
19.3.0-canary-b618bbb4-20261007 08 Oct 2026 C1 malicious MIT No Details →
0.0.0-experimental-d75b0697-20261006 07 Oct 2026 C1 malicious MIT No Details →
19.3.0-canary-d75b0697-20261006 07 Oct 2026 C1 malicious MIT No Details →
0.0.0-experimental-17eca7b0-20261006 06 Oct 2026 C1 malicious MIT No Details →
19.3.0-canary-17eca7b0-20261006 06 Oct 2026 C1 malicious MIT No Details →
0.0.0-experimental-278794d7-20261002 02 Oct 2026 C1 malicious MIT No Details →
19.3.0-canary-278794d7-20261002 02 Oct 2026 C1 malicious MIT No Details →
0.0.0-experimental-7c6ac13e-20260929 29 Sep 2026 C1 malicious MIT No Details →
19.3.0-canary-7c6ac13e-20260929 29 Sep 2026 C1 malicious MIT No Details →
19.3.0-canary-d083ec1d-20260922 23 Sep 2026 C1 malicious MIT No Details →
0.0.0-experimental-d083ec1d-20260922 23 Sep 2026 C1 malicious MIT No Details →
19.3.0-canary-8b0da1c6-20260922 22 Sep 2026 C1 malicious MIT No Details →
0.0.0-experimental-8b0da1c6-20260922 22 Sep 2026 C1 malicious MIT No Details →
0.0.0-experimental-59aff3e1-20260918 18 Sep 2026 C1 malicious MIT No Details →
19.3.0-canary-59aff3e1-20260918 18 Sep 2026 C1 malicious MIT No Details →
19.3.0-canary-2b19aecd-20260916 16 Sep 2026 C1 malicious MIT No Details →
0.0.0-experimental-2b19aecd-20260916 16 Sep 2026 C1 malicious MIT No Details →
0.0.0-experimental-ff8f88fc-20260915 15 Sep 2026 C1 malicious MIT No Details →
19.3.0-canary-ff8f88fc-20260915 15 Sep 2026 C1 malicious MIT No Details →
0.0.0-experimental-9b938532-20260914 14 Sep 2026 C1 malicious MIT No Details →
19.3.0-canary-9b938532-20260914 14 Sep 2026 C1 malicious MIT No Details →
19.3.0-canary-019019be-20260911 11 Sep 2026 C1 malicious MIT No Details →
0.0.0-experimental-019019be-20260911 11 Sep 2026 C1 malicious MIT No Details →
0.0.0-experimental-82c44beb-20260910 10 Sep 2026 C1 malicious MIT No Details →
19.3.0-canary-82c44beb-20260910 10 Sep 2026 C1 malicious MIT No Details →
19.3.0 09 Sep 2026 C1 malicious MIT No Details →
19.3.0-canary-1d34f91d-20260909 09 Sep 2026 C1 malicious MIT No Details →
0.0.0-experimental-1d34f91d-20260909 09 Sep 2026 C1 malicious MIT No Details →
0.0.0-experimental-6c0e1047-20260908 08 Sep 2026 C1 malicious MIT No Details →
19.3.0-canary-6c0e1047-20260908 08 Sep 2026 C1 malicious MIT No Details →
19.3.0-canary-f1f7ed2a-20260904 07 Sep 2026 C1 malicious MIT No Details →
0.0.0-experimental-f1f7ed2a-20260904 07 Sep 2026 C1 malicious MIT No Details →
0.0.0-experimental-8425b691-20260904 04 Sep 2026 C1 malicious MIT No Details →
19.3.0-canary-8425b691-20260904 04 Sep 2026 C1 malicious MIT No Details →
0.0.0-experimental-d9f4e76b-20260903 03 Sep 2026 C1 malicious MIT No Details →
19.3.0-canary-d9f4e76b-20260903 03 Sep 2026 C1 malicious MIT No Details →
19.3.0-canary-f4e439e1-20260902 02 Sep 2026 C1 malicious MIT No Details →
0.0.0-experimental-f4e439e1-20260902 02 Sep 2026 C1 malicious MIT No Details →
19.3.0-canary-21c89c9f-20260901 01 Sep 2026 C1 malicious MIT No Details →
0.0.0-experimental-21c89c9f-20260901 01 Sep 2026 C1 malicious MIT No Details →
0.0.0-experimental-ff7445e6-20260831 31 Aug 2026 C1 malicious MIT No Details →
19.3.0-canary-ff7445e6-20260831 31 Aug 2026 C1 malicious MIT No Details →
0.0.0-experimental-2dc7da79-20260828 28 Aug 2026 C1 malicious MIT No Details →
19.3.0-canary-2dc7da79-20260828 28 Aug 2026 C1 malicious MIT No Details →
0.0.0-experimental-29d9d318-20260826 27 Aug 2026 C1 malicious MIT No Details →
19.3.0-canary-29d9d318-20260826 27 Aug 2026 C1 malicious MIT No Details →
0.0.0-experimental-a1124489-20260826 26 Aug 2026 C1 malicious MIT No Details →
19.3.0-canary-a1124489-20260826 26 Aug 2026 C1 malicious MIT No Details →
0.0.0-experimental-f789f203-20260825 25 Aug 2026 C1 malicious MIT No Details →
19.3.0-canary-f789f203-20260825 25 Aug 2026 C1 malicious MIT No Details →
0.0.0-experimental-bd6ea412-20260824 24 Aug 2026 C1 malicious MIT No Details →
19.3.0-canary-bd6ea412-20260824 24 Aug 2026 C1 malicious MIT No Details →
19.3.0-canary-eafeac09-20260819 20 Aug 2026 C1 malicious MIT No Details →
0.0.0-experimental-eafeac09-20260819 20 Aug 2026 C1 malicious MIT No Details →
0.0.0-experimental-eb8feb71-20260814 14 Aug 2026 C1 malicious MIT No Details →
19.3.0-canary-eb8feb71-20260814 14 Aug 2026 C1 malicious MIT No Details →
0.0.0-experimental-beef6d60-20260813 13 Aug 2026 C1 malicious MIT No Details →
19.3.0-canary-beef6d60-20260813 13 Aug 2026 C1 malicious MIT No Details →
0.0.0-experimental-22e4f993-20260811 12 Aug 2026 C1 malicious MIT No Details →
19.3.0-canary-22e4f993-20260811 12 Aug 2026 C1 malicious MIT No Details →
0.0.0-experimental-bfb7a768-20260811 11 Aug 2026 C1 malicious MIT No Details →
19.3.0-canary-bfb7a768-20260811 11 Aug 2026 C1 malicious MIT No Details →
19.3.0-canary-807d21fd-20260810 10 Aug 2026 C1 malicious MIT No Details →
0.0.0-experimental-807d21fd-20260810 10 Aug 2026 C1 malicious MIT No Details →
0.0.0-experimental-ec61f187-20260806 07 Aug 2026 C1 malicious MIT No Details →
19.3.0-canary-ec61f187-20260806 07 Aug 2026 C1 malicious MIT No Details →
0.0.0-experimental-11eddecd-20260805 05 Aug 2026 C1 malicious MIT No Details →
19.3.0-canary-11eddecd-20260805 05 Aug 2026 C1 malicious MIT No Details →
0.0.0-experimental-7dfc7ccd-20260803 03 Aug 2026 C1 malicious MIT No Details →
19.3.0-canary-7dfc7ccd-20260803 03 Aug 2026 C1 malicious MIT No Details →
0.0.0-experimental-cbb046ab-20260731 31 Jul 2026 C1 malicious MIT No Details →
19.3.0-canary-cbb046ab-20260731 31 Jul 2026 C1 malicious MIT No Details →
0.0.0-experimental-0f42eac2-20260730 30 Jul 2026 C1 malicious MIT No Details →
19.3.0-canary-0f42eac2-20260730 30 Jul 2026 C1 malicious MIT No Details →
0.0.0-experimental-6cb4322d-20260729 30 Jul 2026 C1 malicious MIT No Details →
19.3.0-canary-6cb4322d-20260729 30 Jul 2026 C1 malicious MIT No Details →
0.0.0-experimental-1724e9ce-20260729 29 Jul 2026 C1 malicious MIT No Details →
19.3.0-canary-1724e9ce-20260729 29 Jul 2026 C1 malicious MIT No Details →
0.0.0-experimental-96fcba90-20260728 28 Jul 2026 C1 malicious MIT No Details →
19.3.0-canary-96fcba90-20260728 28 Jul 2026 C1 malicious — No Details →
0.0.0-experimental-756fdd47-20260727 27 Jul 2026 C1 malicious — No Details →
19.3.0-canary-756fdd47-20260727 27 Jul 2026 C1 malicious — No Details →
0.0.0-experimental-28cd4bb0-20260723 23 Jul 2026 C1 malicious — No Details →
19.3.0-canary-28cd4bb0-20260723 23 Jul 2026 C1 malicious — No Details →
0.0.0-experimental-711c445b-20260722 22 Jul 2026 C1 malicious — No Details →
19.3.0-canary-711c445b-20260722 22 Jul 2026 C1 malicious — No Details →
0.0.0-experimental-81e442ea-20260721 21 Jul 2026 C1 malicious — No Details →
19.3.0-canary-81e442ea-20260721 21 Jul 2026 C1 malicious — No Details →
19.0.8 21 Jul 2026 C1 malicious — No Details →
19.1.9 21 Jul 2026 C1 malicious — No Details →
19.2.8 21 Jul 2026 C1 malicious — No Details →
0.0.0-experimental-83840902-20260719 20 Jul 2026 C1 malicious — No Details →
19.3.0-canary-83840902-20260719 20 Jul 2026 C1 malicious — No Details →
0.0.0-experimental-172742b4-20260716 17 Jul 2026 C1 malicious — No Details →
19.3.0-canary-172742b4-20260716 17 Jul 2026 C1 malicious — No Details →
0.0.0-experimental-95f4603e-20260716 16 Jul 2026 C1 malicious — No Details →
19.3.0-canary-95f4603e-20260716 16 Jul 2026 C1 malicious — No Details →
0.0.0-experimental-b740af25-20260715 15 Jul 2026 C1 malicious — No Details →
19.3.0-canary-b740af25-20260715 15 Jul 2026 C1 malicious — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 2
  • 2024 1

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

03 Vulnerabilities

Recorded vulnerabilities for react

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2013-7035: Cross-Site Scripting in react 6.5 medium 0.4.2 04 Sep 2020
Cross-Site Scripting Vulnerability in react N/A high 0.14.0 04 Sep 2020
Malicious Code in React (npm) - MAL-2024-2929 N/A critical No fix published 25 Jun 2024

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

Is react safe to use?

Vulert records 3 vulnerabilities for react in npm: 1 critical, 1 high, 1 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate. 1 are malicious-package vulnerabilities: the published package itself contained hostile code, not only a bug.

What is react's Vulert package health score?

Vulert scores react 15/100, which reads as critical. 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). The current release contains malicious code, which caps this score.

Is the latest version of react affected?

Yes. 19.3.1, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does react have?

3 vulnerabilities are recorded for react in the npm ecosystem: 1 critical, 1 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 react vulnerabilities disclosed?

0 vulnerabilities were recorded for react in the last 12 months, and the oldest entry in this database dates to 04 Sep 2020. 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 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.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor react for upcoming vulnerabilities?

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