CVE-2026-67214

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

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 functions is exposed to a denial-of-service condition.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity75% × 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 19, 2026

Advisory Details (3)

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

nanoid before 5.1.16 Infinite Loop via Negative Size in non-secure module | Advisories | VulnCheck

https://www.vulncheck.com/advisories/nanoid-before-infinite-loop-via-negative-size-in-non-secure-module
github_commit Patch Available

commit 6ccc67bbaba7 (ai/nanoid)

Patch available: ai/nanoid 5.1.16 (contains commit 6ccc67bbaba7)

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

5.1.16

Patch available: ai/nanoid 5.1.16

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

Vendor Advisories for CVE-2026-67214(4)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatgrafana13-1-main-13.1.1-0.3.hum12026-07-29redhat
redhatjaeger-main-2.20.0-0.7.hum12026-07-29redhat

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.9+~cs9.3.30-1 (8 versions)8.5.15+~cs9.3.39-1—
npm(1)
PackageVulnerable rangeFixed inDependents
nanoid—5.1.16—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 27× in last 7d / 69× 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-25 23:27 UTCEG score recompute
  2. 2026-08-25 23:27 UTCVendor advisory
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-25 10:56 UTCVendor advisory
  5. 2026-08-24 22:48 UTCEG score recompute
  6. 2026-08-24 22:48 UTCVendor advisory
  7. 2026-08-24 10:40 UTCEG score recompute
  8. 2026-08-24 10:40 UTCVendor advisory
  9. 2026-08-23 22:31 UTCVendor advisory
  10. 2026-08-23 10:24 UTCEG score recompute
  11. 2026-08-23 10:24 UTCVendor advisory
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 22:14 UTCVendor advisory
  14. 2026-08-22 10:06 UTCEG score recompute
  15. 2026-08-22 10:06 UTCVendor advisory
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 21:55 UTCVendor advisory
  18. 2026-08-21 09:45 UTCEG score recompute
  19. 2026-08-21 09:45 UTCVendor advisory
  20. 2026-08-20 22:56 UTCEPSS rescore
  21. 2026-08-20 21:37 UTCVendor advisory
  22. 2026-08-20 09:29 UTCVendor advisory
  23. 2026-08-19 21:21 UTCVendor advisory
  24. 2026-08-19 20:38 UTCEG score recompute
  25. 2026-08-19 20:38 UTCVendor advisory
Show 44 more
  1. 2026-08-19 17:04 UTCEPSS rescore
  2. 2026-08-19 15:40 UTCVendor advisory
  3. 2026-08-19 03:33 UTCVendor advisory
  4. 2026-08-18 14:54 UTCEG score recompute▲ 1.60
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 22:33 UTCEG score recompute
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-16 20:57 UTCEG score recompute
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-15 19:22 UTCEG score recompute
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 17:46 UTCEG score recompute
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-12 14:22 UTCEG score recompute
  15. 2026-08-12 13:51 UTCEPSS rescore
  16. 2026-08-11 12:46 UTCEG score recompute
  17. 2026-08-11 00:00 UTCEPSS rescore
  18. 2026-08-10 11:10 UTCEG score recompute
  19. 2026-08-09 13:47 UTCEPSS rescore
  20. 2026-08-08 08:00 UTCEG score recompute
  21. 2026-08-07 06:24 UTCEG score recompute
  22. 2026-08-07 06:24 UTCGHSA enrichment
  23. 2026-08-06 13:47 UTCEPSS rescore
  24. 2026-08-06 04:49 UTCEG score recompute
  25. 2026-08-06 04:49 UTCGHSA enrichment
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-05 19:17 UTCEPSS rescore
  28. 2026-08-05 03:13 UTCEG score recompute
  29. 2026-08-05 03:13 UTCGHSA enrichment
  30. 2026-08-04 15:10 UTCEPSS rescore
  31. 2026-08-04 10:39 UTCEPSS rescore
  32. 2026-08-04 01:33 UTCGHSA enrichment
  33. 2026-08-02 23:57 UTCGHSA enrichment
  34. 2026-08-01 22:22 UTCEG score recompute
  35. 2026-08-01 22:22 UTCGHSA enrichment
  36. 2026-08-01 04:16 UTCEPSS rescore
  37. 2026-07-31 20:45 UTCGHSA enrichment
  38. 2026-07-30 19:09 UTCGHSA enrichment
  39. 2026-07-30 16:58 UTCEG score recompute
  40. 2026-07-30 16:58 UTCGHSA enrichment
  41. 2026-07-30 16:28 UTCEPSS rescore
  42. 2026-07-29 14:19 UTCEG score recompute
  43. 2026-07-29 13:58 UTCEG score recompute
  44. 2026-07-29 13:57 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-67214?
CVE-2026-67214 is a high vulnerability published on July 29, 2026. 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…
When was CVE-2026-67214 disclosed?
CVE-2026-67214 was first published in the National Vulnerability Database on July 29, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67214 actively exploited?
CVE-2026-67214 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 74.7% of all scored CVEs.
What is the CVSS score of CVE-2026-67214?
CVE-2026-67214 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-67214?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67214, 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-67214

Explore →

Is Your Infrastructure Affected by CVE-2026-67214?

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

Start Free Scan →Browse All CVEs