Is nanoid 3.3 vulnerable?
npm · 21 releases from 3.3.0 to 3.3.20 · latest nanoid is 6.0.2 · checked 1 Nov 2026
No known advisories in the last release
nanoid 3.3.20, the last 3.3 release, has no known advisories. 4 advisories affect earlier 3.3.x releases, so update to 3.3.20.
npm install nanoid@3.3.20Fixed within 3.3.x, affecting earlier releases
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
Which of your client projects are still on nanoid 3.3?
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.