CVE-2026-67214: nanoid (Nano ID) before 3.3.16 and 5.1.16 contains an infinite loop in the customAlphabet and nanoid functions

Q: How do I fix CVE-2026-67214?

nanoid: upgrade to 3.3.16, 5.1.16. Exact commands for each OS are on this page.

Q: Is CVE-2026-67214 being exploited?

CVE-2026-67214 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-67214 affect?

CVE-2026-67214 affects nanoid. Severity is medium (CVSS 5.9). nanoid (Nano ID) before 3.3.16 and 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 fro

Q: How urgent is CVE-2026-67214?

Priority 32/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.9REMOTEUPGRADE

CVE-2026-67214 is a medium-severity flaw (CVSS 5.9) affecting nanoid. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

nanoid (Nano ID) before 3.3.16 and 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 functi

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.3% (top 75%)
CISA exploited list	No
Weakness	CWE-835
Published	2026-07-29
Last modified	2026-10-23

Publisher (CNA): VulnCheck · Vendor: nanoid project

Am I affected?

Timeline

2026-07-29 14:16 UTCPublished CVE record published
2026-10-23 23:10 UTCUpdated Record last modified

nanoid project nanoid UPGRADE

Affected: < 3.3.16 · >= 4.0.0 and < 5.1.16

Fixed in: 3.3.16, 5.1.16

Safe to downgrade to: a release before 4.0.0

1. Check installed version

npm ls nanoid

2. UPGRADE to 3.3.16

npm install nanoid@">=3.3.16"

3. If no update is available yet, DOWNGRADE to a release before 4.0.0

npm view nanoid versions npm install nanoid@"<4.0.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-67214?

nanoid: upgrade to 3.3.16, 5.1.16. Exact commands for each OS are on this page.

Is CVE-2026-67214 being exploited?

CVE-2026-67214 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-67214 affect?

CVE-2026-67214 affects nanoid. Severity is medium (CVSS 5.9). nanoid (Nano ID) before 3.3.16 and 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 fro

How urgent is CVE-2026-67214?

Priority 32/100. Remotely exploitable, no login, no user action

Related CVEs

CVE-2026-67213 MEDIUM 5.9 UPGRADE nanoid (Nano ID) before 5.1.6 contains an infinite loop in the customAlphabet and customRandom functions

References

← Back to latest CVEs