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% (24th percentile of EPSS-scored CVEs). 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.3%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100CISA SSVC

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%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
24th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 29, 2026

Last Modified

October 8, 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(20)

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

Patch Availability(23)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatquay/quay-rhel9:17906902982026-10-01redhat
redhatautomation-platform-ui-0:2.6.14-1.el9ap2026-09-23redhat
redhatquay/quay-rhel8:17885938432026-09-22redhat
redhatquay/quay-rhel9:17895637532026-09-21redhat
redhatrhdh/rhdh-hub-rhel9:17895542852026-09-21redhat
redhatquay/quay-rhel8:17885943762026-09-10redhat
redhatquay/quay-rhel8:17885618412026-09-09redhat
redhatquay/quay-rhel8:17885955742026-09-08redhat
redhatansible-automation-platform/automation-portal:17887835912026-09-08redhat
redhatansible-automation-platform/automation-portal:17887757482026-09-08redhat
redhatquay/quay-rhel8:17881917552026-09-03redhat
redhatdevspaces/openvsx-rhel9:17877591452026-09-01redhat
redhatdiscovery/discovery-ui-rhel9:17882061962026-08-31redhat
redhatrhacm2/console-rhel9:17876870622026-08-26redhat
redhatrhacm2/console-rhel9:17873351052026-08-26redhat
redhatrhacm2/console-rhel9:17873392492026-08-26redhat
redhatrhacm2/console-rhel9:17873392482026-08-26redhat
redhatmulticluster-engine/console-mce-rhel9:17872590482026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17870793592026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17866688562026-08-25redhat
redhatgrafana13-2-main-13.2.0-0.1.1.hum12026-08-24redhat
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 rangeFix by version rangeDependents
node-mocha10.0.0+ds1+~cs28.5.6-1 ... 9.2.2+ds1+~cs28.5.6-2 (30 versions)
  • every version on: no fix on record
—
node-postcss8.2.1+~cs5.3.23-8 ... 8.5.9+~cs9.3.30-1 (31 versions)
  • every version on: no fix on record
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
node-mocha—
  • every version up to 9.1.4+ds1+~cs28.2.8-1: fixed in 9.1.4+ds1+~cs28.2.8-1
—
node-postcss8.4.20+~cs8.0.23-1 ... 8.5.9+~cs9.3.30-1 (19 versions)
  • every version on: no fix on record
—
Debian:13(2)
PackageVulnerable rangeFix by version rangeDependents
node-mocha—
  • every version up to 9.1.4+ds1+~cs28.2.8-1: fixed in 9.1.4+ds1+~cs28.2.8-1
—
node-postcss8.4.49+~cs9.2.32-1 ... 8.5.9+~cs9.3.30-1 (15 versions)
  • every version on: no fix on record
—
Debian:14(2)
PackageVulnerable rangeFix by version rangeDependents
node-mocha—
  • every version up to 9.1.4+ds1+~cs28.2.8-1: fixed in 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)
  • every version up to 8.5.15+~cs9.3.39-1: fixed in 8.5.15+~cs9.3.39-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
nanoid—
  • every version up to 3.3.16: fixed in 3.3.16
  • 4.0.0 up to 5.1.16: fixed in 5.1.16
—

Weakness Classification(1)

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

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 17× in last 7d / 74× 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.

Showing the most recent 100 of 184 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:13 UTCEPSS rescore
  3. 2026-10-08 16:38 UTCVendor advisory
  4. 2026-10-08 15:44 UTCEG score recompute
  5. 2026-10-08 15:44 UTCVendor advisory
  6. 2026-10-07 23:48 UTCEPSS rescore
  7. 2026-10-07 00:01 UTCEG score recompute
  8. 2026-10-07 00:01 UTCVendor advisory
  9. 2026-10-06 15:18 UTCEPSS rescore
  10. 2026-10-05 20:53 UTCEG score recompute
  11. 2026-10-05 20:53 UTCVendor advisory
  12. 2026-10-05 17:43 UTCEPSS rescore
  13. 2026-10-05 02:37 UTCEG score recompute
  14. 2026-10-05 02:37 UTCVendor advisory
  15. 2026-10-04 23:22 UTCEPSS rescore
  16. 2026-10-04 07:02 UTCEG score recompute
  17. 2026-10-04 07:02 UTCVendor advisory
  18. 2026-10-03 14:26 UTCEPSS rescore
  19. 2026-10-02 17:58 UTCEG score recompute
  20. 2026-10-02 17:58 UTCVendor advisory
  21. 2026-10-02 17:56 UTCEPSS rescore
  22. 2026-10-01 19:50 UTCEPSS rescore
  23. 2026-10-01 05:58 UTCVendor advisory
  24. 2026-09-30 17:08 UTCEG score recompute
  25. 2026-09-30 17:08 UTCVendor advisory
Show 75 more
  1. 2026-09-30 15:03 UTCEPSS rescore
  2. 2026-09-29 07:36 UTCEG score recompute
  3. 2026-09-29 07:36 UTCVendor advisory
  4. 2026-09-28 13:52 UTCEPSS rescore
  5. 2026-09-28 03:17 UTCEG score recompute
  6. 2026-09-28 03:17 UTCVendor advisory
  7. 2026-09-27 13:48 UTCEPSS rescore
  8. 2026-09-26 15:59 UTCEPSS rescore
  9. 2026-09-25 05:41 UTCEG score recompute
  10. 2026-09-25 05:41 UTCVendor advisory
  11. 2026-09-24 09:58 UTCVendor advisory
  12. 2026-09-23 21:50 UTCEG score recompute
  13. 2026-09-23 21:50 UTCVendor advisory
  14. 2026-09-23 17:54 UTCEPSS rescore
  15. 2026-09-23 03:57 UTCEG score recompute
  16. 2026-09-23 03:57 UTCVendor advisory
  17. 2026-09-22 15:49 UTCEG score recompute
  18. 2026-09-22 15:49 UTCVendor advisory
  19. 2026-09-20 20:16 UTCEPSS rescore
  20. 2026-09-20 00:23 UTCEG score recompute
  21. 2026-09-20 00:23 UTCVendor advisory
  22. 2026-09-19 04:55 UTCEG score recompute
  23. 2026-09-19 04:55 UTCVendor advisory
  24. 2026-09-18 19:28 UTCEPSS rescore
  25. 2026-09-18 15:17 UTCVendor advisory
  26. 2026-09-18 01:42 UTCEG score recompute
  27. 2026-09-18 01:42 UTCVendor advisory
  28. 2026-09-17 01:36 UTCEG score recompute
  29. 2026-09-17 01:36 UTCVendor advisory
  30. 2026-09-16 14:08 UTCEPSS rescore
  31. 2026-09-16 05:49 UTCEG score recompute
  32. 2026-09-16 05:49 UTCVendor advisory
  33. 2026-09-16 05:15 UTCEPSS rescore
  34. 2026-09-15 08:08 UTCEG score recompute
  35. 2026-09-15 08:08 UTCVendor advisory
  36. 2026-09-14 09:18 UTCVendor advisory
  37. 2026-09-13 21:11 UTCEG score recompute
  38. 2026-09-13 21:11 UTCVendor advisory
  39. 2026-09-13 08:53 UTCVendor advisory
  40. 2026-09-12 20:45 UTCEG score recompute
  41. 2026-09-12 20:45 UTCVendor advisory
  42. 2026-09-12 08:37 UTCVendor advisory
  43. 2026-09-11 20:25 UTCEG score recompute
  44. 2026-09-11 20:25 UTCVendor advisory
  45. 2026-09-11 14:53 UTCEPSS rescore
  46. 2026-09-11 09:37 UTCEPSS rescore
  47. 2026-09-11 08:00 UTCVendor advisory
  48. 2026-09-10 19:52 UTCEG score recompute
  49. 2026-09-10 19:52 UTCVendor advisory
  50. 2026-09-10 07:14 UTCVendor advisory
  51. 2026-09-09 07:50 UTCEG score recompute
  52. 2026-09-09 07:50 UTCVendor advisory
  53. 2026-09-08 22:01 UTCEPSS rescore
  54. 2026-09-07 20:52 UTCEG score recompute
  55. 2026-09-07 20:52 UTCVendor advisory
  56. 2026-09-07 16:01 UTCEPSS rescore
  57. 2026-09-06 22:41 UTCEG score recompute
  58. 2026-09-06 22:41 UTCVendor advisory
  59. 2026-09-06 13:47 UTCEPSS rescore
  60. 2026-09-06 07:16 UTCVendor advisory
  61. 2026-09-05 19:07 UTCEG score recompute
  62. 2026-09-05 19:07 UTCVendor advisory
  63. 2026-09-05 15:31 UTCEPSS rescore
  64. 2026-09-05 05:16 UTCEG score recompute
  65. 2026-09-05 05:16 UTCVendor advisory
  66. 2026-09-04 11:56 UTCEG score recompute
  67. 2026-09-04 11:56 UTCVendor advisory
  68. 2026-09-04 05:07 UTCEPSS rescore
  69. 2026-09-02 14:12 UTCEPSS rescore
  70. 2026-09-01 22:47 UTCEG score recompute
  71. 2026-09-01 22:47 UTCVendor advisory
  72. 2026-09-01 13:54 UTCEPSS rescore
  73. 2026-09-01 04:40 UTCEPSS rescore
  74. 2026-08-31 23:59 UTCVendor advisory
  75. 2026-08-30 23:35 UTCEG score recompute

Related CVEs(same product + same vendor + same CWE)

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 on July 29, 2026, with the most recent update on October 8, 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.3% probability of exploitation in the next 30 days (24th percentile of EPSS-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?
A fix for CVE-2026-67214 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-67214 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs