VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

react-toastify: vulnerability history, versions and safety

react-toastify 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 react-toastify vulnerabilities

Vulert verdict on react-toastify 11.1.0 i

Updated on 23 Oct 2026

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

Package health score 79/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 11.1.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 584 packages i
  • Stars 13,445 i
  • OpenSSF scorecard 2/10 i
  • Last release 6 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-toastify, 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
11.1.0 19 Apr 2026 none MIT — Details →
11.0.5 24 Feb 2025 none MIT — Details →
11.0.4 24 Feb 2025 none MIT — Details →
11.0.4-0 10 Feb 2025 none MIT — Details →
11.0.3 15 Jan 2025 none MIT — Details →
11.0.2 19 Dec 2024 none MIT — Details →
11.0.1-react17 18 Dec 2024 none MIT — Details →
11.0.1 18 Dec 2024 none MIT — Details →
11.0.0 16 Dec 2024 none MIT — Details →
11.0.0-0 16 Dec 2024 none MIT — Details →
10.0.7-5 13 Dec 2024 none MIT — Details →
10.0.7-4 12 Dec 2024 none MIT — Details →
10.0.7-3 12 Dec 2024 none MIT — Details →
10.0.7-2 11 Dec 2024 none MIT — Details →
10.0.7-1 10 Dec 2024 none MIT — Details →
10.0.7-0 10 Dec 2024 none MIT — Details →
10.0.6 13 Oct 2024 none MIT — Details →
10.0.5 15 Mar 2024 none MIT — Details →
10.0.4 21 Jan 2024 none MIT — Details →
10.0.3 16 Jan 2024 none MIT — Details →
10.0.2-debug 16 Jan 2024 none MIT — Details →
10.0.2 16 Jan 2024 none MIT — Details →
10.0.1 15 Jan 2024 none MIT — Details →
10.0.0 14 Jan 2024 none MIT — Details →
10.0.0-beta.1 04 Aug 2023 none MIT — Details →
9.1.3 14 May 2023 none MIT — Details →
9.1.2-rsc 14 May 2023 none MIT — Details →
9.1.2 21 Mar 2023 none MIT — Details →
9.1.1 02 Nov 2022 none MIT — Details →
9.1.0 01 Nov 2022 none MIT — Details →
9.0.8 07 Aug 2022 none MIT — Details →
9.0.7-fix-autoclose-2 04 Aug 2022 none MIT — Details →
9.0.7-fix-autoclose-1 04 Aug 2022 none MIT — Details →
9.0.7 19 Jul 2022 none MIT — Details →
9.0.6-vite-1 18 Jul 2022 none MIT — Details →
9.0.6 17 Jul 2022 none MIT — Details →
9.0.5 20 Jun 2022 none MIT — Details →
9.0.4 07 Jun 2022 none MIT — Details →
9.0.3 31 May 2022 none MIT — Details →
9.0.2 29 May 2022 none MIT — Details →
9.0.1 05 May 2022 none MIT — Details →
9.0.0 03 May 2022 none MIT — Details →
9.0.0-rc-2 04 Apr 2022 none MIT — Details →
9.0.0-rc-1 02 Apr 2022 none MIT — Details →
9.0.0-POC 01 Mar 2022 none MIT — Details →
8.2.0 14 Feb 2022 none MIT — Details →
8.1.1 01 Feb 2022 none MIT — Details →
8.1.0 03 Nov 2021 none MIT — Details →
8.0.3 24 Sep 2021 none MIT — Details →
8.0.2-with-side-effects 31 Aug 2021 none MIT — Details →
8.0.2 30 Aug 2021 none MIT — Details →
8.0.1 27 Aug 2021 none MIT — Details →
8.0.0 26 Aug 2021 none MIT — Details →
8.0.0-rc1 26 Aug 2021 none MIT — Details →
7.0.4 23 Apr 2021 none MIT — Details →
7.0.3 01 Feb 2021 none MIT — Details →
7.0.2 28 Jan 2021 none MIT — Details →
7.0.1 27 Jan 2021 none MIT — Details →
7.0.0 25 Jan 2021 none MIT — Details →
7.0.0-rc3 24 Jan 2021 none MIT — Details →
7.0.0-rc2 24 Jan 2021 none MIT — Details →
7.0.0-rc1 22 Jan 2021 none MIT — Details →
6.2.0 08 Dec 2020 none MIT — Details →
6.1.0 06 Nov 2020 none MIT — Details →
6.0.9 05 Oct 2020 none MIT — Details →
6.0.8 02 Jul 2020 none MIT — Details →
6.0.7 02 Jul 2020 none MIT — Details →
6.0.6 21 Jun 2020 none MIT — Details →
6.0.5 20 May 2020 none MIT — Details →
6.0.4 13 May 2020 none MIT — Details →
6.0.3 13 May 2020 none MIT — Details →
6.0.2 12 May 2020 none MIT — Details →
6.0.1 11 May 2020 none MIT — Details →
6.0.0 10 May 2020 none MIT — Details →
6.0.0-rc.3 09 May 2020 none MIT — Details →
6.0.0-rc.2-1 06 May 2020 none MIT — Details →
6.0.0-rc.2 05 May 2020 none MIT — Details →
6.0.0-rc.1 04 May 2020 none MIT — Details →
6.0.0-rc.0 19 Apr 2020 none MIT — Details →
5.5.0 30 Dec 2019 none MIT — Details →
5.4.1 10 Nov 2019 none MIT — Details →
5.4.0 23 Sep 2019 none MIT — Details →
5.3.2 15 Jul 2019 none MIT — Details →
5.3.1 20 Jun 2019 none MIT — Details →
5.3.0 18 Jun 2019 none MIT — Details →
5.2.1 30 May 2019 none MIT — Details →
5.2.0 29 May 2019 none MIT — Details →
5.1.1 22 May 2019 none MIT — Details →
5.1.0 16 Apr 2019 none MIT — Details →
5.0.1 11 Apr 2019 none MIT — Details →
5.0.1-rc.1 11 Apr 2019 none MIT — Details →
5.0.0 08 Apr 2019 none MIT — Details →
5.0.0-rc.6 02 Apr 2019 none MIT — Details →
5.0.0-rc.5 31 Mar 2019 none MIT — Details →
5.0.0-rc.4 31 Mar 2019 none MIT — Details →
5.0.0-rc.3 26 Mar 2019 none MIT — Details →
5.0.0-rc.2 26 Mar 2019 none MIT — Details →
5.0.0-rc.1 25 Mar 2019 none MIT — Details →
4.5.2 02 Jan 2019 none MIT — Details →
4.5.1 18 Dec 2018 none MIT — Details →
4.5.0 15 Dec 2018 none — — Details →
4.5.0-rc.1 15 Dec 2018 none — — Details →
4.4.3 12 Nov 2018 none — — Details →
4.4.2 11 Nov 2018 none — — Details →
4.4.1 09 Nov 2018 none — — Details →
4.4.0 01 Oct 2018 none — — Details →
4.3.2 24 Sep 2018 none — — Details →
4.3.1 09 Sep 2018 none — — Details →
4.3.0 02 Sep 2018 none — — Details →
4.2.3 29 Aug 2018 none — — Details →
4.2.2 29 Aug 2018 none — — Details →
4.2.1 29 Aug 2018 none — — Details →
4.2.0 13 Aug 2018 none — — Details →
4.1.0 07 Jun 2018 none — — Details →
4.0.2 04 Jun 2018 none — — Details →
4.0.1 02 May 2018 none — — Details →
4.0.0 02 May 2018 none — — Details →
4.0.0-rc.6 02 May 2018 none — — Details →
4.0.0-rc.5 20 Apr 2018 none — — Details →
4.0.0-rc.4 16 Apr 2018 none — — Details →

The newest 120 of 170 versions Vulert tracks. 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 react-toastify

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

Is react-toastify safe to use?

Vulert has no vulnerabilities on record for react-toastify 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 react-toastify's Vulert package health score?

Vulert scores react-toastify 79/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-toastify affected?

No. 11.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 react-toastify should I use?

11.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 react-toastify have?

0 vulnerabilities are recorded for react-toastify 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 react-toastify vulnerabilities disclosed?

0 vulnerabilities were recorded for react-toastify 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 react-toastify 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-toastify for upcoming vulnerabilities?

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