nanoid: non-secure generators can loop indefinitely with negative size
Published 29 Jul 2026 · Updated 10 Sept 2026
Affected packages
- Affected
- <3.3.16
- Fixed in
- 3.3.16
npm install nanoid@3.3.16- Affected
- >=4.0.0 <5.1.16
- Fixed in
- 5.1.16
npm install nanoid@5.1.16Details
nanoid (Nano ID) before 5.1.16 contains an infinite loop in the customAlphabet and nanoid functions of its non-secure module (nanoid/non-secure). When these functions are given a negative size, the loop counter is decremented from a negative value and never reaches its termination condition, spinning indefinitely and hanging the calling thread. An application that passes an unvalidated, attacker-controlled negative size to these functions is exposed to a denial-of-service condition.
Is GHSA-28wg-ghj8-5hjv in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected nanoid, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-67214
- Linkgithub.com/ai/nanoid/pull/600
- Linkgithub.com/ai/nanoid/pull/601
- Linkgithub.com/ai/nanoid/commit/6ccc67bbaba71d3d77a21d9b636f4171a268ce49
- Linkgithub.com/ai/nanoid/commit/e835c9b71eab832bc6106944bdd26ea96cf2c66d
- Packagegithub.com/ai/nanoid
- Linkgithub.com/ai/nanoid/releases/tag/5.1.16
- Linkwww.vulncheck.com/advisories/nanoid-before-infinite-loop-via-negative-size-in-non-secure-module
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.