VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

nanoid: vulnerability history, versions and safety

nanoid is a package in the npm ecosystem. Vulert records 5 vulnerabilities for it across 95 releases, from Jan 2022 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H3 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 01 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all nanoid vulnerabilities

Vulert verdict on nanoid 6.0.2 i

Updated on 22 Oct 2026

Good news: 6.0.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 5.

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

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

  • Current release 6.0.2 — unaffected i
  • Vulnerabilities on record 5 over 4 years · 3 in the last year i
  • Latest disclosure 01 Sep 2026 i
  • Highest CVSS 7.4 i
  • With no published fix 0 i
  • Depended on by 2,896 packages i
  • Stars 27,105 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 nanoid, 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
6.0.2 05 Oct 2026 none MIT — Details →
3.3.20 05 Oct 2026 none MIT — Details →
3.3.19 10 Sep 2026 none MIT — Details →
3.3.18 07 Aug 2026 none MIT — Details →
6.0.1 03 Aug 2026 none MIT — Details →
3.3.17 03 Aug 2026 none MIT — Details →
6.0.0 12 Jul 2026 none MIT — Details →
3.3.16 12 Jul 2026 H1 MIT Yes Details →
5.1.16 24 Jun 2026 none MIT — Details →
3.3.15 21 Jun 2026 H2 MIT Yes Details →
5.1.15 20 Jun 2026 none MIT — Details →
3.3.14 20 Jun 2026 H2 MIT Yes Details →
5.1.14 18 Jun 2026 none MIT — Details →
5.1.13 18 Jun 2026 none MIT — Details →
5.1.12 18 Jun 2026 none MIT — Details →
3.3.13 18 Jun 2026 H2 MIT Yes Details →
5.1.11 30 Apr 2026 none MIT — Details →
3.3.12 30 Apr 2026 H2 MIT Yes Details →
5.1.10 30 Apr 2026 none MIT — Details →
5.1.9 15 Apr 2026 none MIT — Details →
5.1.8 15 Apr 2026 none MIT — Details →
5.1.7 15 Mar 2026 none MIT — Details →
5.1.6 22 Sep 2025 none MIT — Details →
5.1.5 18 Mar 2025 none MIT — Details →
3.3.11 18 Mar 2025 H3 MIT Yes Details →
5.1.4 15 Mar 2025 none MIT — Details →
3.3.10 15 Mar 2025 H3 MIT Yes Details →
5.1.3 07 Mar 2025 none MIT — Details →
3.3.9 07 Mar 2025 H3 MIT Yes Details →
5.1.2 22 Feb 2025 none MIT — Details →
5.1.1 22 Feb 2025 none MIT — Details →
5.1.0 14 Feb 2025 none MIT — Details →
5.0.9 26 Nov 2024 none MIT — Details →
3.3.8 26 Nov 2024 H3 MIT Yes Details →
5.0.8 28 Oct 2024 M1 MIT Yes Details →
5.0.7 07 Apr 2024 M1 MIT Yes Details →
5.0.6 20 Feb 2024 M1 MIT Yes Details →
5.0.5 01 Feb 2024 M1 MIT Yes Details →
5.0.4 02 Dec 2023 M1 MIT Yes Details →
5.0.3 06 Nov 2023 M1 MIT Yes Details →
3.3.7 06 Nov 2023 H3 MIT Yes Details →
5.0.2 15 Oct 2023 M1 MIT Yes Details →
5.0.1 12 Sep 2023 M1 MIT Yes Details →
5.0.0 12 Sep 2023 M1 MIT Yes Details →
3.3.6 26 Mar 2023 H3 MIT Yes Details →
3.3.5 26 Mar 2023 H3 MIT Yes Details →
4.0.2 26 Mar 2023 M1 MIT Yes Details →
4.0.1 05 Feb 2023 M1 MIT Yes Details →
4.0.0 08 Jun 2022 M1 MIT Yes Details →
3.3.4 03 May 2022 H3 MIT Yes Details →
3.3.3 18 Apr 2022 H3 MIT Yes Details →
3.3.2 28 Mar 2022 H3 MIT Yes Details →
3.3.1 16 Feb 2022 H3 MIT Yes Details →
3.3.0 14 Feb 2022 H3 MIT Yes Details →
3.2.0 16 Jan 2022 H3 MIT Yes Details →
3.1.32 12 Jan 2022 H3 MIT Yes Details →
3.1.31 11 Jan 2022 H3 MIT Yes Details →
3.1.30 13 Oct 2021 H3 M1 MIT Yes Details →
3.1.29 05 Oct 2021 H3 M1 MIT Yes Details →
3.1.28 26 Sep 2021 H3 M1 MIT Yes Details →
3.1.27 26 Sep 2021 H3 M1 MIT Yes Details →
3.1.26 26 Sep 2021 H3 M1 MIT Yes Details →
3.1.25 12 Aug 2021 H3 M1 MIT Yes Details →
3.1.24 11 Aug 2021 H3 M1 MIT Yes Details →
3.1.23 10 May 2021 H3 M1 MIT Yes Details →
3.1.22 15 Mar 2021 H3 M1 MIT Yes Details →
3.1.21 11 Mar 2021 H3 M1 MIT Yes Details →
3.1.20 01 Dec 2020 H3 M1 MIT Yes Details →
3.1.19 01 Dec 2020 H3 M1 MIT Yes Details →
3.1.18 20 Nov 2020 H3 M1 MIT Yes Details →
3.1.17 20 Nov 2020 H3 M1 MIT Yes Details →
3.1.16 26 Oct 2020 H3 M1 MIT Yes Details →
3.1.15 23 Oct 2020 H3 M1 MIT Yes Details →
3.1.14 23 Oct 2020 H3 M1 MIT Yes Details →
3.1.13 21 Oct 2020 H3 M1 MIT Yes Details →
3.1.12 29 Jul 2020 H3 M1 MIT Yes Details →
3.1.11 27 Jul 2020 H3 M1 MIT Yes Details →
3.1.10 13 Jun 2020 H3 M1 MIT Yes Details →
3.1.9 17 May 2020 H3 M1 MIT Yes Details →
3.1.8 16 May 2020 H3 M1 MIT Yes Details →
3.1.7 11 May 2020 H3 M1 MIT Yes Details →
3.1.6 08 May 2020 H3 M1 MIT Yes Details →
3.1.5 05 May 2020 H3 M1 MIT Yes Details →
3.1.4 04 May 2020 H3 M1 MIT Yes Details →
3.1.3 10 Apr 2020 H3 M1 MIT Yes Details →
3.1.2 10 Apr 2020 H3 M1 MIT Yes Details →
3.1.1 10 Apr 2020 H3 M1 MIT Yes Details →
3.1.0 10 Apr 2020 H3 M1 MIT Yes Details →
3.0.2 29 Mar 2020 H3 M1 MIT Yes Details →
3.0.1 28 Mar 2020 H3 M1 MIT Yes Details →
3.0.0 26 Mar 2020 H3 M1 MIT Yes Details →
2.1.11 30 Jan 2020 H3 MIT Yes Details →
2.1.10 22 Jan 2020 H3 MIT Yes Details →
2.1.9 07 Jan 2020 H3 MIT Yes Details →
2.1.8 14 Dec 2019 H3 MIT Yes Details →
2.1.7 16 Nov 2019 H3 MIT Yes Details →
2.1.6 24 Oct 2019 H3 MIT Yes Details →
2.1.5 23 Oct 2019 H3 MIT Yes Details →
2.1.4 17 Oct 2019 H3 MIT Yes Details →
2.1.3 11 Oct 2019 H3 MIT Yes Details →
2.1.2 03 Oct 2019 H3 — Yes Details →
2.1.1 11 Sep 2019 H3 — Yes Details →
2.1.0 30 Aug 2019 H3 — Yes Details →
2.0.4 25 Aug 2019 H3 — Yes Details →
2.0.3 21 May 2019 H3 — Yes Details →
2.0.2 16 May 2019 H3 — Yes Details →
2.0.1 14 Jan 2019 H3 — Yes Details →
2.0.0 04 Nov 2018 H3 — Yes Details →
1.3.4 04 Nov 2018 H3 — Yes Details →
1.3.3 31 Oct 2018 H3 — Yes Details →
1.3.2 31 Oct 2018 H3 — Yes Details →
1.3.1 20 Oct 2018 H3 — Yes Details →
1.3.0 12 Oct 2018 H3 — Yes Details →
1.2.6 02 Oct 2018 H3 — Yes Details →
1.2.5 29 Sep 2018 H3 — Yes Details →
1.2.4 26 Sep 2018 H3 — Yes Details →
1.2.3 04 Sep 2018 H3 — Yes Details →
1.2.2 28 Aug 2018 H3 — Yes Details →
1.2.1 16 Aug 2018 H3 — Yes Details →
1.2.0 10 Aug 2018 H3 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2024 1
  • 2026 3

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

03 Vulnerabilities

Recorded vulnerabilities for nanoid

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-73086: nanoid Integer Overflow Vulnerability Leading to Predictable ID Generation 7.4 high 3.3.12 01 Sep 2026
CVE-2026-67213: nanoid Package Infinite Loop Vulnerability Due to Zero Size Input 5.9 high 3.3.17 29 Jul 2026
CVE-2026-67214: nanoid Package Infinite Loop Vulnerability Due to Negative Size Input 5.9 high 3.3.16 29 Jul 2026
CVE-2021-23566: Information Exposure in nanoid 5.5 medium 3.1.31 21 Jan 2022
CVE-2024-55565: Infinite Loop Vulnerability in nanoid Package 4.3 medium 5.0.9 09 Dec 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 →

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.

Add Vulert as a Preferred Source

Questions

About nanoid

Is nanoid safe to use?

Vulert records 5 vulnerabilities for nanoid in npm: 0 critical, 3 high, 2 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 nanoid's Vulert package health score?

Vulert scores nanoid 81/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 nanoid affected?

No. 6.0.2, 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 nanoid should I use?

6.0.2 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 nanoid have?

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

3 vulnerabilities were recorded for nanoid in the last 12 months, and the oldest entry in this database dates to 21 Jan 2022. 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 nanoid 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 nanoid for upcoming vulnerabilities?

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