Is CVE-2026-67213 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-67213 being exploited in the wild.

How severe is CVE-2026-67213?

Medium severity, with a CVSS score of 5.9, published 29 July 2026.

Which products and versions are affected?

nanoid (npm) SEMVER:introduced=0,fixed=3.3.18.

Is there a fix for CVE-2026-67213?

Yes. nanoid (npm): upgrade to 3.3.18 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-67213 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-67213?

Check whether you run Nano ID Project Nano ID or nanoid (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-67213: nanoid infinite loop in customAlphabet and customRandom

CVE-2026-67213 · Severity: medium · CVSS 5.9 · Published 2026-07-29

Nano ID is a popular JavaScript library for generating secure, unique identifiers. When the customAlphabet or customRandom functions are called with a size parameter of zero, the library enters an infinite loop that hangs the application thread, causing a denial-of-service. An attacker who can control the size parameter passed to these functions can crash applications using vulnerable versions.

Technologies: nanoid (npm). Vendors: npm.

Quick answers

Is CVE-2026-67213 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-67213 being exploited in the wild.
How severe is CVE-2026-67213?: Medium severity, with a CVSS score of 5.9, published 29 July 2026.
Which products and versions are affected?: nanoid (npm) SEMVER:introduced=0,fixed=3.3.18.
Is there a fix for CVE-2026-67213?: Yes. nanoid (npm): upgrade to 3.3.18 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67213 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-67213?: Check whether you run Nano ID Project Nano ID or nanoid (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

nanoid (npm): upgrade to 3.3.18 or later
```
npm install nanoid@3.3.18
```

Technical details

This vulnerability (CWE-835: Infinite Loop) exists in the customAlphabet and customRandom functions of the Nano ID library. The generation loop in these functions fails to handle a zero or negative size parameter, resulting in an exit condition that can never be satisfied. When an application passes an attacker-controlled size value of 0 to these functions without prior validation, the thread executing the function will hang indefinitely, consuming CPU resources and rendering the application unresponsive. The vulnerability affects all versions before 3.3.18 (for the 0.x–3.x branch) and before 5.1.6 (for the 4.x–5.x branch). Patches have been released that add explicit validation to reject zero and negative size parameters, either by throwing an error or returning an empty string depending on the code path.

Affected products

ai nanoid before 3.3.18 and 4.0.0 before 5.1.6

Identifiers

CVE-2026-67213
GHSA-2v37-7h3g-55p8

Timeline

2026-07-29: disclosed: Vulnerability published to advisories
2026-08-03: patched: Fixes released in versions 3.3.18 and 5.1.6

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.