Vulnerability Database · npm · Package report

@react-native-community/cli: vulnerability history, versions and safety

@react-native-community/cli is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 111 releases, first recorded in Nov 2025. 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 C1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 03 Nov 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on @react-native-community/cli 20.2.0 i

Updated on 23 Oct 2026

Good news: 20.2.0, 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 Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 20.2.0 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 03 Nov 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 15 packages i
  • Stars 2,941 i
  • OpenSSF scorecard 3/10 i
  • Last release 3 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-native-community/cli, 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
21.0.0-alpha.1 29 Sep 2026 none MIT — Details →
20.2.0 25 Jun 2026 none MIT — Details →
20.1.3 24 Mar 2026 none MIT — Details →
20.1.2 24 Feb 2026 none MIT — Details →
20.1.1 28 Jan 2026 none MIT — Details →
20.1.0 07 Jan 2026 none MIT — Details →
17.0.1 05 Nov 2025 C1 MIT Yes Details →
18.0.1 05 Nov 2025 C1 MIT Yes Details →
19.1.2 05 Nov 2025 C1 MIT Yes Details →
20.0.2 09 Sep 2025 none MIT — Details →
20.0.1 20 Aug 2025 none MIT — Details →
20.0.0 11 Aug 2025 none MIT — Details →
19.1.1 24 Jul 2025 C1 MIT Yes Details →
20.0.0-alpha.2 24 Jul 2025 C1 MIT Yes Details →
19.1.0 09 Jul 2025 C1 MIT Yes Details →
20.0.0-alpha.0 03 Jul 2025 C1 MIT Yes Details →
19.0.0 29 Apr 2025 C1 MIT Yes Details →
16.0.3 17 Apr 2025 C1 MIT Yes Details →
19.0.0-alpha.2 17 Apr 2025 C1 MIT Yes Details →
19.0.0-alpha.0 06 Mar 2025 C1 MIT Yes Details →
18.0.0 05 Mar 2025 C1 MIT Yes Details →
17.0.0 05 Mar 2025 C1 MIT Yes Details →
16.0.2 12 Dec 2024 C1 MIT Yes Details →
14.1.2 12 Dec 2024 C1 MIT Yes Details →
15.1.3 12 Dec 2024 C1 MIT Yes Details →
16.0.1 12 Dec 2024 C1 MIT Yes Details →
16.0.0 04 Dec 2024 C1 MIT Yes Details →
15.1.2 08 Nov 2024 C1 MIT Yes Details →
15.1.1 07 Nov 2024 C1 MIT Yes Details →
15.1.0 05 Nov 2024 C1 MIT Yes Details →
15.0.1 31 Oct 2024 C1 MIT Yes Details →
15.0.1-alpha.0 30 Oct 2024 C1 MIT Yes Details →
15.0.0 24 Oct 2024 C1 MIT Yes Details →
14.1.1 12 Sep 2024 C1 MIT Yes Details →
15.0.0-alpha.2 09 Sep 2024 C1 MIT Yes Details →
15.0.0-alpha.0 09 Sep 2024 C1 MIT Yes Details →
14.1.0 09 Sep 2024 C1 MIT Yes Details →
14.0.1 19 Aug 2024 C1 MIT Yes Details →
14.0.0 18 Jul 2024 C1 MIT Yes Details →
14.0.0-alpha.11 26 Jun 2024 C1 MIT Yes Details →
14.0.0-alpha.10 25 Jun 2024 C1 MIT Yes Details →
14.0.0-alpha.9 24 Jun 2024 C1 MIT Yes Details →
14.0.0-alpha.8 21 Jun 2024 C1 MIT Yes Details →
14.0.0-alpha.7 20 Jun 2024 C1 MIT Yes Details →
14.0.0-alpha.6 20 Jun 2024 C1 MIT Yes Details →
12.3.7 05 Jun 2024 C1 MIT Yes Details →
13.6.9 05 Jun 2024 C1 MIT Yes Details →
13.6.8 03 Jun 2024 C1 MIT Yes Details →
13.6.7 03 Jun 2024 C1 MIT Yes Details →
14.0.0-alpha.5 09 May 2024 C1 MIT Yes Details →
13.6.6 25 Apr 2024 C1 MIT Yes Details →
14.0.0-alpha.4 25 Apr 2024 C1 MIT Yes Details →
13.6.5 18 Apr 2024 C1 MIT Yes Details →
14.0.0-alpha.3 18 Apr 2024 C1 MIT Yes Details →
13.6.4 27 Mar 2024 C1 MIT Yes Details →
14.0.0-alpha.2 27 Mar 2024 C1 MIT Yes Details →
13.6.3 20 Mar 2024 C1 MIT Yes Details →
14.0.0-alpha.1 20 Mar 2024 C1 MIT Yes Details →
14.0.0-alpha.0 11 Mar 2024 C1 MIT Yes Details →
13.6.2 11 Mar 2024 C1 MIT Yes Details →
13.6.1 22 Feb 2024 C1 MIT Yes Details →
10.2.7 19 Feb 2024 C1 MIT Yes Details →
11.4.1 19 Feb 2024 C1 MIT Yes Details →
12.3.6 19 Feb 2024 C1 MIT Yes Details →
13.6.0 19 Feb 2024 C1 MIT Yes Details →
11.4.0 05 Feb 2024 C1 MIT Yes Details →
12.3.5 05 Feb 2024 C1 MIT Yes Details →
13.5.2 05 Feb 2024 C1 MIT Yes Details →
12.3.4 31 Jan 2024 C1 MIT Yes Details →
13.5.1 23 Jan 2024 C1 MIT Yes Details →
12.3.3 16 Jan 2024 C1 MIT Yes Details →
13.5.1-alpha.0 15 Jan 2024 C1 MIT Yes Details →
12.3.2 15 Jan 2024 C1 MIT Yes Details →
13.5.0 15 Jan 2024 C1 MIT Yes Details →
12.3.1 10 Jan 2024 C1 MIT Yes Details →
13.4.0 08 Jan 2024 C1 MIT Yes Details →
13.3.0 08 Jan 2024 C1 MIT Yes Details →
13.2.0 22 Dec 2023 C1 MIT Yes Details →
12.3.0 13 Dec 2023 C1 MIT Yes Details →
13.1.0 13 Dec 2023 C1 MIT Yes Details →
12.2.1 11 Dec 2023 C1 MIT Yes Details →
13.0.1 11 Dec 2023 C1 MIT Yes Details →
13.0.0 04 Dec 2023 C1 MIT Yes Details →
12.2.0 30 Nov 2023 C1 MIT Yes Details →
12.1.1 20 Nov 2023 C1 MIT Yes Details →
12.1.0 17 Nov 2023 C1 MIT Yes Details →
9.3.5 06 Nov 2023 C1 MIT Yes Details →
10.2.6 06 Nov 2023 C1 MIT Yes Details →
11.3.10 03 Nov 2023 C1 MIT Yes Details →
12.0.0 31 Oct 2023 C1 MIT Yes Details →
11.3.9 13 Oct 2023 C1 MIT Yes Details →
12.0.0-alpha.18 03 Oct 2023 C1 MIT Yes Details →
12.0.0-alpha.17 27 Sep 2023 C1 MIT Yes Details →
12.0.0-alpha.16 26 Sep 2023 C1 MIT Yes Details →
12.0.0-alpha.15 21 Sep 2023 C1 MIT Yes Details →
12.0.0-alpha.14 21 Sep 2023 C1 MIT Yes Details →
12.0.0-alpha.13 14 Sep 2023 C1 MIT Yes Details →
11.3.8 12 Sep 2023 C1 MIT Yes Details →
12.0.0-alpha.12 12 Sep 2023 C1 MIT Yes Details →
12.0.0-alpha.11 18 Aug 2023 C1 MIT Yes Details →
12.0.0-alpha.10 17 Aug 2023 C1 — Yes Details →
12.0.0-alpha.9 11 Aug 2023 C1 — Yes Details →
12.0.0-alpha.8 09 Aug 2023 C1 — Yes Details →
11.3.7 09 Aug 2023 C1 — Yes Details →
9.3.4 17 Jul 2023 C1 — Yes Details →
11.3.6 11 Jul 2023 C1 — Yes Details →
12.0.0-alpha.7 11 Jul 2023 C1 — Yes Details →
12.0.0-alpha.6 30 Jun 2023 C1 — Yes Details →
11.3.5 30 Jun 2023 C1 — Yes Details →
11.3.4 29 Jun 2023 C1 — Yes Details →
11.3.3 22 Jun 2023 C1 — Yes Details →
12.0.0-alpha.5 22 Jun 2023 C1 — Yes Details →
10.2.5 16 Jun 2023 C1 — Yes Details →
12.0.0-alpha.4 12 Jun 2023 C1 — Yes Details →
11.3.2 12 Jun 2023 C1 — Yes Details →
10.2.4 12 Jun 2023 C1 — Yes Details →
10.2.3 12 Jun 2023 C1 — Yes Details →
9.3.3 12 Jun 2023 C1 — Yes Details →
8.0.7 12 Jun 2023 C1 — Yes Details →
11.3.1 25 May 2023 C1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for @react-native-community/cli

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 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-native-community/cli

Is @react-native-community/cli safe to use?

Vulert records 1 vulnerabilities for @react-native-community/cli in npm: 1 critical, 0 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-native-community/cli's Vulert package health score?

Vulert scores @react-native-community/cli 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-native-community/cli affected?

No. 20.2.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 @react-native-community/cli should I use?

20.2.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 @react-native-community/cli have?

1 vulnerability is recorded for @react-native-community/cli in the npm ecosystem: 1 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 @react-native-community/cli vulnerabilities disclosed?

1 vulnerability was recorded for @react-native-community/cli in the last 12 months, and the oldest entry in this database dates to 03 Nov 2025. 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-native-community/cli 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-native-community/cli for upcoming vulnerabilities?

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