CVE-2026-67213
Nano ID <5.1.6 loops indefinitely on zero-size input, causing thread hang (DoS).
Is CVE-2026-67213 being exploited?
Not confirmed. CVE-2026-67213 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-67213?
CVE-2026-67213 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67213?
Yes. A fix has been recorded for CVE-2026-67213. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67213 affect?
CVE-2026-67213 affects nanoid <5.1.6, Node.js/JavaScript applications using nanoid, Backend services and APIs using nanoid. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67213?
Upgrade nanoid to >=5.1.6 and validate/whitelist size inputs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Denial-of-service: attacker-supplied size=0 to customAlphabet/customRandom causes infinite loop, hanging the calling thread.
Patch when possible
- affected>= 3.0.0 and < 3.3.17
- affected>= 5.0.0 and < 5.1.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.