Vulnerability Database · npm · Package report

react-dev-utils: vulnerability history, versions and safety

react-dev-utils is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 116 releases, from Jan 2019 to Jul 2026. 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 H1 M2
i
1 with no fix published

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

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

Most recent disclosure 06 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on react-dev-utils 12.0.1 i

Updated on 23 Oct 2026

Careful: 12.0.1 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 12.0.1 — affected i
  • Vulnerabilities on record 3 over 7 years · 1 in the last year i
  • Latest disclosure 06 Jul 2026 i
  • Highest CVSS 7.3 i
  • With no published fix 1 i
  • Depended on by 40,410 packages i
  • Stars 103,236 i
  • OpenSSF scorecard 3/10 i
  • Last release 54 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 react-dev-utils, 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
12.1.0-next.26 14 Feb 2025 M1 MIT No Details →
12.0.1 12 Apr 2022 M1 MIT No Details →
12.1.0-next.14 12 Apr 2022 M1 MIT No Details →
12.0.0 14 Dec 2021 M1 MIT No Details →
12.0.0-next.60 14 Dec 2021 M1 MIT No Details →
12.0.0-next.58 08 Dec 2021 M1 MIT No Details →
12.0.0-next.47 04 Oct 2021 M1 MIT No Details →
12.0.0-next.37 01 Sep 2021 M1 MIT No Details →
12.0.0-next.31 04 Aug 2021 M1 MIT No Details →
11.0.4 08 Mar 2021 M1 MIT No Details →
11.0.3 22 Feb 2021 M2 MIT No Details →
11.0.2 03 Feb 2021 M2 MIT No Details →
11.0.1 23 Nov 2020 M2 MIT No Details →
11.0.0 23 Oct 2020 M2 MIT No Details →
11.0.0-next.117 23 Oct 2020 M2 MIT No Details →
11.0.0-next.116 23 Oct 2020 M2 MIT No Details →
11.0.0-next.98 16 Sep 2020 M2 MIT No Details →
11.0.0-next.96 16 Sep 2020 M2 MIT No Details →
11.0.0-next.77 05 Aug 2020 M2 MIT No Details →
11.0.0-next.64 30 Jul 2020 M2 MIT No Details →
10.2.1 21 Mar 2020 M2 MIT No Details →
10.2.0 14 Feb 2020 M2 MIT No Details →
10.1.0 31 Jan 2020 M2 MIT No Details →
10.0.0 05 Dec 2019 M2 MIT No Details →
9.2.0-next.80 04 Dec 2019 M2 MIT No Details →
9.2.0-next.62 14 Nov 2019 M2 MIT No Details →
9.2.0-next.39 24 Oct 2019 M2 MIT No Details →
9.2.0-next.38 24 Oct 2019 M2 MIT No Details →
9.1.0 03 Oct 2019 M2 MIT No Details →
9.0.4 19 Sep 2019 M2 MIT No Details →
9.0.3 13 Aug 2019 M2 MIT No Details →
9.0.2 09 Aug 2019 M2 MIT No Details →
9.0.1 08 May 2019 M2 MIT No Details →
9.0.0 22 Apr 2019 M2 MIT No Details →
9.0.0-next.68 17 Apr 2019 M2 MIT No Details →
9.0.0-next.b0cbf2ca 15 Mar 2019 M2 MIT No Details →
8.0.0 07 Mar 2019 M2 MIT No Details →
7.0.5 07 Mar 2019 M2 MIT No Details →
7.0.4 06 Mar 2019 M2 MIT No Details →
7.0.3 11 Feb 2019 M2 MIT No Details →
7.0.2 10 Feb 2019 M2 MIT No Details →
7.0.1 04 Jan 2019 M2 MIT No Details →
7.0.1-next.6a95aae9 04 Jan 2019 M2 MIT No Details →
7.0.0 23 Dec 2018 M2 MIT No Details →
6.1.1 01 Nov 2018 M2 MIT No Details →
6.1.0 30 Oct 2018 M2 MIT No Details →
6.0.6-next.c662dfb0 25 Oct 2018 M2 MIT No Details →
6.0.6-next.9b4009d7 24 Oct 2018 M2 MIT No Details →
6.0.5 14 Oct 2018 M2 MIT No Details →
5.0.3 14 Oct 2018 M2 MIT No Details →
4.2.3 14 Oct 2018 M2 MIT No Details →
3.1.3 14 Oct 2018 M2 BSD-3-Clause No Details →
2.0.3 14 Oct 2018 M2 BSD-3-Clause No Details →
1.0.5 14 Oct 2018 M2 BSD-3-Clause No Details →
6.0.4 03 Oct 2018 M2 MIT No Details →
6.0.3 02 Oct 2018 M2 MIT No Details →
6.0.2 01 Oct 2018 M2 MIT No Details →
6.0.1 28 Sep 2018 M2 MIT No Details →
6.0.0 26 Sep 2018 M2 MIT No Details →
6.0.0-next.fb6e6f70 25 Sep 2018 M2 MIT No Details →
6.0.0-next.2150693d 21 Sep 2018 M2 MIT No Details →
6.0.0-next.a671462c 24 Aug 2018 M2 MIT No Details →
4.2.2 24 Aug 2018 M2 MIT No Details →
3.1.2 24 Aug 2018 M2 BSD-3-Clause No Details →
2.0.2 24 Aug 2018 M2 BSD-3-Clause No Details →
1.0.4 24 Aug 2018 M2 BSD-3-Clause No Details →
5.0.2 22 Aug 2018 M2 MIT No Details →
6.0.0-next.3e165448 18 Jun 2018 M2 MIT No Details →
6.0.0-next.66cc7a90 21 Apr 2018 M2 MIT No Details →
5.0.1 04 Apr 2018 M2 MIT No Details →
6.0.0-next.b2fd8db8 21 Mar 2018 M2 MIT No Details →
6.0.0-next.47d2d941 07 Feb 2018 M2 MIT No Details →
6.0.0-next.03604a46 07 Feb 2018 M2 MIT No Details →
6.0.0-next.9754a231 18 Jan 2018 M2 MIT No Details →
6.0.0-next.096703ab 18 Jan 2018 M2 MIT No Details →
5.0.0 15 Jan 2018 M2 MIT No Details →
4.2.1 31 Oct 2017 M2 MIT No Details →
4.2.0 30 Oct 2017 M2 MIT No Details →
4.1.0 27 Sep 2017 M2 MIT No Details →
4.0.1 02 Sep 2017 M2 BSD-3-Clause No Details →
4.0.0 28 Aug 2017 M2 BSD-3-Clause No Details →
3.1.1 10 Aug 2017 M2 BSD-3-Clause No Details →
3.1.0 09 Aug 2017 M2 BSD-3-Clause No Details →
3.0.2 29 Jun 2017 M2 BSD-3-Clause No Details →
3.0.1 28 Jun 2017 M2 BSD-3-Clause No Details →
3.0.0-alpha.60ae2b6d 28 Jun 2017 M2 BSD-3-Clause No Details →
3.0.0 27 May 2017 M2 BSD-3-Clause No Details →
2.0.1 24 May 2017 M2 BSD-3-Clause No Details →
2.0.0 22 May 2017 M2 BSD-3-Clause No Details →
1.0.3 21 May 2017 H1 M2 BSD-3-Clause No Details →
1.0.2 20 May 2017 H1 M2 BSD-3-Clause No Details →
1.0.1 19 May 2017 H1 M2 BSD-3-Clause No Details →
1.0.0 19 May 2017 H1 M2 BSD-3-Clause No Details →
1.0.0-alpha.55afd862 18 May 2017 M2 BSD-3-Clause No Details →
1.0.0-alpha.02968ecd 18 May 2017 M2 BSD-3-Clause No Details →
1.0.0-alpha.0d0536f9 18 May 2017 M2 BSD-3-Clause No Details →
1.0.0-alpha.c82c4f05 18 May 2017 M2 BSD-3-Clause No Details →
1.0.0-alpha.e280254d 16 May 2017 M2 BSD-3-Clause No Details →
1.0.0-alpha.134d2297 16 May 2017 M2 BSD-3-Clause No Details →
1.0.0-alpha.dadf93b2 16 May 2017 M2 BSD-3-Clause No Details →
1.0.0-alpha.58689133 16 May 2017 M2 — No Details →
0.6.0-alpha.f55d2212 15 Mar 2017 M2 — No Details →
0.5.2 06 Mar 2017 M2 — No Details →
0.5.1 26 Feb 2017 M2 — No Details →
0.5.0 11 Feb 2017 M2 — No Details →
0.4.2 11 Dec 2016 M2 — No Details →
0.4.1 07 Dec 2016 M2 — No Details →
0.4.0 03 Dec 2016 M2 — No Details →
0.3.0-alpha.9c45b252 22 Nov 2016 M1 — No Details →
0.3.0-alpha.e756d73a 29 Oct 2016 M1 — No Details →
0.3.0 22 Oct 2016 M1 — No Details →
0.2.1 27 Sep 2016 M1 — No Details →
0.2.0 25 Sep 2016 M1 — No Details →
0.1.1 23 Sep 2016 M1 — No Details →
0.1.0 23 Sep 2016 M1 — No Details →
0.0.0 23 Sep 2016 M1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2021 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for react-dev-utils

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →

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 react-dev-utils

Is react-dev-utils safe to use?

Vulert records 3 vulnerabilities for react-dev-utils in npm: 0 critical, 1 high, 2 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is react-dev-utils's Vulert package health score?

Vulert scores react-dev-utils 60/100, which reads as usable, but worth attention. 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 has a vulnerability with no published fix, which caps this score.

Is the latest version of react-dev-utils affected?

Yes. 12.0.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.

Which version of react-dev-utils should I use?

12.0.1 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 react-dev-utils have?

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

1 vulnerability was recorded for react-dev-utils in the last 12 months, and the oldest entry in this database dates to 04 Jan 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-dev-utils 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-dev-utils for upcoming vulnerabilities?

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