CVE-2026-67213

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2026-07-29. a secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

A fix is available — apply it.

nanoid (Nano ID) before 5.1.6 contains an infinite loop in the customAlphabet and customRandom functions. When these functions are configured with a size of 0, the internal generation loop never satisfies its exit condition and spins indefinitely, hanging the calling thread. An application that passes an unvalidated, attacker-controlled size of 0 to these functions is exposed to a denial-of-service condition.

CVSS v3
5.9
EG Score
5.9(high)
EG Risk
27(Track)
EG Risk 27/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

July 29, 2026

Last Modified

August 10, 2026

Advisory Details (3)

Auto-updated Jul 29, 2026
Patch available. Sources: github_release, github_commit.
generic

nanoid before 5.1.6 Infinite Loop via Zero Size in customAlphabet and customRandom | Advisories | VulnCheck

https://www.vulncheck.com/advisories/nanoid-before-infinite-loop-via-zero-size-in-customalphabet-and-customrandom
github_commit Patch Available

commit cb3626d0f334 (ai/nanoid)

Patch available: ai/nanoid 5.1.6 (contains commit cb3626d0f334)

https://github.com/ai/nanoid/commit/cb3626d0f3342fdf179cd425fd9c4fbb92c7d0e7
github_release Patch Available

5.1.6

Patch available: ai/nanoid 5.1.6

https://github.com/ai/nanoid/releases/tag/5.1.6

Vendor Advisories for CVE-2026-67213(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgrafana13-1-main-13.1.1-0.3.hum12026-07-29redhat
redhatjaeger-main-2.20.0-0.6.hum12026-07-28redhat
redhatgrafana12-4-main-12.4.6-0.2.hum12026-07-28redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(9 across 5 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
node-mocha10.0.0+ds1+~cs28.5.6-1 ... 9.2.2+ds1+~cs28.5.6-2 (30 versions)——
node-postcss8.2.1+~cs5.3.23-8 ... 8.5.9+~cs9.3.30-1 (31 versions)——
Debian:12(2)
PackageVulnerable rangeFixed inDependents
node-mocha—9.1.4+ds1+~cs28.2.8-1—
node-postcss8.4.20+~cs8.0.23-1 ... 8.5.9+~cs9.3.30-1 (17 versions)——
Debian:13(2)
PackageVulnerable rangeFixed inDependents
node-mocha—9.1.4+ds1+~cs28.2.8-1—
node-postcss8.4.49+~cs9.2.32-1 ... 8.5.9+~cs9.3.30-1 (13 versions)——
Debian:14(2)
PackageVulnerable rangeFixed inDependents
node-mocha—9.1.4+ds1+~cs28.2.8-1—
node-postcss8.4.49+~cs9.2.32-1, 8.5.6+~cs9.3.28-18.5.8+~cs9.3.30-1—
npm(1)
PackageVulnerable rangeFixed inDependents
nanoid—5.1.6—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 17× in last 7d / 45× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-15 15:44 UTCEG score recompute
  2. 2026-08-15 15:44 UTCVendor advisory
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 15:54 UTCEG score recompute
  5. 2026-08-14 15:54 UTCVendor advisory
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-13 16:04 UTCVendor advisory
  8. 2026-08-12 16:09 UTCEG score recompute
  9. 2026-08-12 16:09 UTCVendor advisory
  10. 2026-08-12 13:51 UTCEPSS rescore
  11. 2026-08-11 16:19 UTCEG score recompute
  12. 2026-08-11 16:19 UTCVendor advisory
  13. 2026-08-11 00:00 UTCEPSS rescore
  14. 2026-08-10 16:29 UTCEG score recompute
  15. 2026-08-10 16:10 UTCEG score recompute
  16. 2026-08-09 17:32 UTCEG score recompute
  17. 2026-08-09 13:47 UTCEPSS rescore
  18. 2026-08-08 17:42 UTCEG score recompute
  19. 2026-08-08 16:37 UTCEPSS rescore
  20. 2026-08-07 17:52 UTCEG score recompute
  21. 2026-08-07 17:52 UTCGHSA enrichment
  22. 2026-08-06 18:02 UTCEG score recompute
  23. 2026-08-06 18:02 UTCGHSA enrichment
  24. 2026-08-06 13:47 UTCEPSS rescore
  25. 2026-08-05 19:17 UTCEPSS rescore
Show 20 more
  1. 2026-08-05 19:17 UTCEPSS rescore
  2. 2026-08-05 18:11 UTCGHSA enrichment
  3. 2026-08-04 18:21 UTCEG score recompute
  4. 2026-08-04 18:21 UTCGHSA enrichment
  5. 2026-08-04 15:10 UTCEPSS rescore
  6. 2026-08-04 10:39 UTCEPSS rescore
  7. 2026-08-03 18:31 UTCGHSA enrichment
  8. 2026-08-02 18:41 UTCGHSA enrichment
  9. 2026-08-01 18:51 UTCEG score recompute
  10. 2026-08-01 18:51 UTCGHSA enrichment
  11. 2026-08-01 04:16 UTCEPSS rescore
  12. 2026-07-31 19:00 UTCGHSA enrichment
  13. 2026-07-30 19:09 UTCEG score recompute
  14. 2026-07-30 19:09 UTCGHSA enrichment
  15. 2026-07-30 16:28 UTCEPSS rescore
  16. 2026-07-30 15:42 UTCEG score recompute
  17. 2026-07-30 15:42 UTCGHSA enrichment
  18. 2026-07-29 14:19 UTCEG score recompute
  19. 2026-07-29 13:58 UTCEG score recompute
  20. 2026-07-29 13:57 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-67213?
CVE-2026-67213 is a medium vulnerability published on July 29, 2026. nanoid (Nano ID) before 5.1.6 contains an infinite loop in the customAlphabet and customRandom functions. When these functions are configured with a size of 0, the internal generation loop never satisfies its exit condition and spins indefinitely, hanging the calling thread. An application that…
When was CVE-2026-67213 disclosed?
CVE-2026-67213 was first published in the National Vulnerability Database on July 29, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67213 actively exploited?
CVE-2026-67213 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 75.4% of all scored CVEs.
What is the CVSS score of CVE-2026-67213?
CVE-2026-67213 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-67213?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67213, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-67213

Explore →

Is Your Infrastructure Affected by CVE-2026-67213?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs