VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

create-react-app: vulnerability history, versions and safety

create-react-app is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

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 create-react-app vulnerabilities

Vulert verdict on create-react-app 5.1.0 i

Updated on 23 Oct 2026

Good news: 5.1.0, the version you would install today, has no known vulnerabilities.

Package health score 74/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Moderate

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

  • Current release 5.1.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 51 packages i
  • Stars 103,236 i
  • OpenSSF scorecard 3/10 i
  • Last release 20 months 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 create-react-app, 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
5.1.0 15 Feb 2025 none MIT — Details →
5.1.0-next.26 14 Feb 2025 none MIT — Details →
5.0.1 12 Apr 2022 none MIT — Details →
5.1.0-next.14 12 Apr 2022 none MIT — Details →
5.0.0 14 Dec 2021 none MIT — Details →
5.0.0-next.60 14 Dec 2021 none MIT — Details →
5.0.0-next.59 14 Dec 2021 none MIT — Details →
5.0.0-next.58 08 Dec 2021 none MIT — Details →
5.0.0-next.57 08 Dec 2021 none MIT — Details →
5.0.0-next.47 04 Oct 2021 none MIT — Details →
5.0.0-next.37 01 Sep 2021 none MIT — Details →
5.0.0-next.31 04 Aug 2021 none MIT — Details →
4.0.3 22 Feb 2021 none MIT — Details →
4.0.2 03 Feb 2021 none MIT — Details →
4.0.1 23 Nov 2020 none MIT — Details →
4.0.0 23 Oct 2020 none MIT — Details →
4.0.0-next.117 23 Oct 2020 none MIT — Details →
4.0.0-next.116 23 Oct 2020 none MIT — Details →
4.0.0-next.98 16 Sep 2020 none MIT — Details →
4.0.0-next.96 16 Sep 2020 none MIT — Details →
4.0.0-next.77 05 Aug 2020 none MIT — Details →
4.0.0-next.64 30 Jul 2020 none MIT — Details →
3.4.1 21 Mar 2020 none MIT — Details →
3.4.0 14 Feb 2020 none MIT — Details →
3.3.1 31 Jan 2020 none MIT — Details →
3.3.0 05 Dec 2019 none MIT — Details →
3.3.0-next.80 04 Dec 2019 none MIT — Details →
3.3.0-next.62 14 Nov 2019 none MIT — Details →
3.3.0-next.39 24 Oct 2019 none MIT — Details →
3.3.0-next.38 24 Oct 2019 none MIT — Details →
3.2.0 03 Oct 2019 none MIT — Details →
3.1.2 19 Sep 2019 none MIT — Details →
3.1.1 13 Aug 2019 none MIT — Details →
3.1.0 09 Aug 2019 none MIT — Details →
3.0.1 08 May 2019 none MIT — Details →
3.0.0 22 Apr 2019 none MIT — Details →
3.0.0-next.68 17 Apr 2019 none MIT — Details →
3.0.0-next.b0cbf2ca 15 Mar 2019 none MIT — Details →
2.1.8 07 Mar 2019 none MIT — Details →
2.1.7 07 Mar 2019 none MIT — Details →
2.1.6 06 Mar 2019 none MIT — Details →
2.1.5 11 Feb 2019 none MIT — Details →
2.1.4 10 Feb 2019 none MIT — Details →
2.1.3 04 Jan 2019 none MIT — Details →
2.1.3-next.6a95aae9 04 Jan 2019 none MIT — Details →
2.1.2 23 Dec 2018 none MIT — Details →
2.1.1 01 Nov 2018 none MIT — Details →
2.1.0 30 Oct 2018 none MIT — Details →
2.0.5-next.c662dfb0 25 Oct 2018 none MIT — Details →
2.0.5-next.9b4009d7 24 Oct 2018 none MIT — Details →
2.0.4 14 Oct 2018 none MIT — Details →
2.0.3 03 Oct 2018 none MIT — Details →
2.0.2 02 Oct 2018 none MIT — Details →
2.0.1 01 Oct 2018 none MIT — Details →
2.0.0 26 Sep 2018 none MIT — Details →
2.0.0-next.fb6e6f70 25 Sep 2018 none MIT — Details →
2.0.0-next.2150693d 21 Sep 2018 none MIT — Details →
2.0.0-next.a671462c 24 Aug 2018 none MIT — Details →
2.0.0-next.3e165448 18 Jun 2018 none MIT — Details →
2.0.0-next.66cc7a90 21 Apr 2018 none MIT — Details →
2.0.0-next.b2fd8db8 21 Mar 2018 none MIT — Details →
1.5.2 09 Feb 2018 none MIT — Details →
2.0.0-next.47d2d941 07 Feb 2018 none MIT — Details →
2.0.0-next.03604a46 07 Feb 2018 none MIT — Details →
1.5.1 18 Jan 2018 none MIT — Details →
2.0.0-next.9754a231 18 Jan 2018 none MIT — Details →
2.0.0-next.096703ab 18 Jan 2018 none MIT — Details →
1.5.0 15 Jan 2018 none MIT — Details →
1.4.3 31 Oct 2017 none MIT — Details →
1.4.2 30 Oct 2017 none MIT — Details →
1.4.1 27 Sep 2017 none MIT — Details →
1.4.0 09 Aug 2017 none BSD-3-Clause — Details →
1.3.3 29 Jun 2017 none BSD-3-Clause — Details →
1.3.2 28 Jun 2017 none BSD-3-Clause — Details →
1.3.1-alpha.60ae2b6d 28 Jun 2017 none BSD-3-Clause — Details →
1.3.1 19 May 2017 none BSD-3-Clause — Details →
1.3.0-alpha.55afd862 18 May 2017 none BSD-3-Clause — Details →
1.3.0-alpha.02968ecd 18 May 2017 none BSD-3-Clause — Details →
1.3.0-alpha.0d0536f9 18 May 2017 none BSD-3-Clause — Details →
1.3.0-alpha.c82c4f05 18 May 2017 none BSD-3-Clause — Details →
1.3.0-alpha.e280254d 16 May 2017 none BSD-3-Clause — Details →
1.3.0-alpha.134d2297 16 May 2017 none BSD-3-Clause — Details →
1.3.0-alpha.dadf93b2 16 May 2017 none BSD-3-Clause — Details →
1.3.0-alpha.58689133 16 May 2017 none BSD-3-Clause — Details →
1.3.0 06 Mar 2017 none BSD-3-Clause — Details →
1.2.1 28 Feb 2017 none BSD-3-Clause — Details →
1.2.0 28 Feb 2017 none BSD-3-Clause — Details →
1.1.0 26 Feb 2017 none BSD-3-Clause — Details →
1.0.4 11 Feb 2017 none BSD-3-Clause — Details →
1.0.3 09 Jan 2017 none BSD-3-Clause — Details →
1.0.2 11 Dec 2016 none BSD-3-Clause — Details →
1.0.1 08 Dec 2016 none BSD-3-Clause — Details →
1.0.0 03 Dec 2016 none BSD-3-Clause — Details →
0.7.0 03 Dec 2016 none BSD-3-Clause — Details →
0.6.0-alpha.9c45b252 22 Nov 2016 none BSD-3-Clause — Details →
0.6.0-alpha.e756d73a 29 Oct 2016 none BSD-3-Clause — Details →
0.6.0 22 Oct 2016 none BSD-3-Clause — Details →
0.5.0 23 Sep 2016 none BSD-3-Clause — Details →
0.4.2-alpha.8f28c56e 19 Sep 2016 none BSD-3-Clause — Details →
0.4.2 18 Sep 2016 none BSD-3-Clause — Details →
0.3.0 01 Sep 2016 none — — Details →
0.2.0 28 Jul 2016 none — — Details →
0.2.0-alpha.1 27 Jul 2016 none — — Details →
0.1.0 22 Jul 2016 none — — Details →
0.0.0 17 Jul 2016 none — — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

No dated vulnerabilities are recorded for this package yet.

03 Vulnerabilities

Recorded vulnerabilities for create-react-app

No vulnerability write-ups match this view

Search all 0 in the database →

No vulnerabilities match this view.

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 create-react-app

Is create-react-app safe to use?

Vulert has no vulnerabilities on record for create-react-app in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.

What is create-react-app's Vulert package health score?

Vulert scores create-react-app 74/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 create-react-app affected?

No. 5.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 create-react-app should I use?

5.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 create-react-app have?

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

0 vulnerabilities were recorded for create-react-app in the last 12 months. 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 create-react-app 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 create-react-app for upcoming vulnerabilities?

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