Is nanoid 3.3.7 vulnerable?

nanoid 3.3.7, a JavaScript package on npm. All 2 versions we track · npm page

4 vulnerabilities, 3 high

Upgrade nanoid from 3.3.7 to 3.3.18 or later; that fixes all of them.

Known vulnerabilities in nanoid 3.3.7

  • High CVSS 5.9

    CVE-2026-67214: nanoid: non-secure generators can loop indefinitely with negative size

    GHSA-28wg-ghj8-5hjv · published 29 Jul 2026 · fixed in 3.3.16

  • High CVSS 5.9

    CVE-2026-67213: nanoid: custom generators can loop indefinitely when size is zero

    GHSA-2v37-7h3g-55p8 · published 29 Jul 2026 · fixed in 3.3.18

  • High CVSS 7.4

    CVE-2026-73086: nanoid: Integer Overflow or Wraparound

    GHSA-xwg4-73v4-xw9w · published 1 Sep 2026 · fixed in 3.3.12

  • Medium CVSS 4.3

    CVE-2024-55565: Predictable results in nanoid generation when given non-integer values

    GHSA-mwcw-c2x4-8c55 · published 9 Dec 2024 · fixed in 3.3.8

How to fix it

With package-lock.json:

npm install nanoid@3.3.18
# if it is an indirect dependency: npm update nanoid (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the package's changelog for breaking changes (especially across major versions), update the lockfile with the package manager (never by hand), and run your tests.

Other versions of nanoid

Newest version we track without known advisories: 3.3.20.

VersionKnown vulnerabilitiesHighest severity
3.3.20 0 None
3.3.7 (this page) 4 High

Every version of nanoid →

Licence

nanoid 3.3.7 declares MIT .

Check your whole project

nanoid is one package among hundreds in a lockfile. Upload your lockfile, or paste a public GitHub repository, and get every vulnerable package with the version that fixes it. Free, and no account needed.

Get emailed about new advisories for nanoid (free, no account)

About this data

Vulnerability data: OSV.dev, last checked 22 November 2026. Licence: deps.dev. AIssue checks the versions on this page every day. Severity comes from the advisory's own rating when it has one, else from its CVSS score.