Is nanoid 3.0 vulnerable?
npm · 3 releases from 3.0.0 to 3.0.2 · latest nanoid is 6.0.2 · checked 1 Nov 2026
Yes: 5 known advisories
Yes. nanoid 3.0.2, the last 3.0 release, is affected by 5 known security advisories (3 high, 2 medium), including CVE-2026-73086, CVE-2026-67214, CVE-2026-67213. Upgrade to 3.3.18 or later to fix all of them.
npm install nanoid@3.3.18Advisories affecting nanoid 3.0.2
nanoid: Integer Overflow or Wraparound
- Affected
- <3.3.12 · >=4.0.0 <5.1.11
- Fixed in
- 3.3.12, 5.1.11
nanoid: non-secure generators can loop indefinitely with negative size
- Affected
- <3.3.16 · >=4.0.0 <5.1.16
- Fixed in
- 3.3.16, 5.1.16
nanoid: custom generators can loop indefinitely when size is zero
- Affected
- <3.3.18 · >=4.0.0 <5.1.6
- Fixed in
- 3.3.18, 5.1.6
Predictable results in nanoid generation when given non-integer values
- Affected
- >=4.0.0 <5.0.9 · <3.3.8
- Fixed in
- 3.3.8, 5.0.9
Exposure of Sensitive Information to an Unauthorized Actor in nanoid
- Affected
- >=3.0.0 <3.1.31
- Fixed in
- 3.1.31
Which of your client projects are still on nanoid 3.0?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact nanoid version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other nanoid versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.