CVE-2026-73086

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.4EG
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.4Exploit: None knownExposed: 0

A fix is available — apply it.

nanoid is a secure, URL-friendly, unique string ID generator for JavaScript. Prior to versions 3.3.12 and 5.1.11, the nanoid(size) function in index.js and index.cjs coerces the user-influenced size parameter to a signed 32-bit integer, allowing a value of 2147483648 to become -2147483648 and corrupt the process-wide CSPRNG poolOffset in fillPool(), which causes subsequent session tokens, CSRF tokens, API keys, and unique identifiers to become the deterministic string "uuuuuuuuuuuuuuuuuuuuu" until the process restarts. This issue is fixed in versions 3.3.12 and 5.1.11.

CVSS v3
7.4
EG Score
7.4(medium)
EG Risk
33(Track)
EG Risk 33/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
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

August 11, 2026

Last Modified

September 9, 2026

Advisory Details (6)

Auto-updated Aug 12, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

Integer Overflow or Wraparound in nanoid · Advisory · ai/nanoid · GitHub

https://github.com/ai/nanoid/security/advisories/GHSA-xwg4-73v4-xw9w
github_release Patch Available

5.1.11

Patch available: ai/nanoid 5.1.11

https://github.com/ai/nanoid/releases/tag/5.1.11
github_release Patch Available

3.3.12

Patch available: ai/nanoid 3.3.12

https://github.com/ai/nanoid/releases/tag/3.3.12
github_commit Patch Available

commit b0036ed60dc9 (ai/nanoid)

Patch available: ai/nanoid 3.3.13 (contains commit b0036ed60dc9)

https://github.com/ai/nanoid/commit/b0036ed60dc9facd7f1191a50dfb3076500202ac
github_commit Patch Available

commit 821dfed7b5db (ai/nanoid)

Patch available: ai/nanoid 3.3.12 (contains commit 821dfed7b5db)

https://github.com/ai/nanoid/commit/821dfed7b5db7f88e92f56c60eef32c8135077c3
github_commit Patch Available

commit 7087969281ca (ai/nanoid)

Patch available: ai/nanoid 5.1.11 (contains commit 7087969281ca)

https://github.com/ai/nanoid/commit/7087969281cab8ba8ae3babf1894e819068b3bb4

Patch Availability(28)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatquay/quay-rhel8:17885943762026-09-10redhat
redhatquay/quay-rhel8:17885618412026-09-09redhat
redhatquay/quay-rhel8:17885955742026-09-08redhat
redhatsatellite/iop-host-inventory-frontend-rhel9:17882609412026-09-03redhat
redhatquay/quay-rhel8:17881917552026-09-03redhat
redhatsatellite/iop-host-inventory-frontend-rhel9:17883222432026-09-03redhat
redhatopenshift4/ose-console-rhel9:17875905232026-09-01redhat
redhatopenshift4/ose-console-rhel9:17877376952026-09-01redhat
redhatdevspaces/code-rhel9:17877627932026-09-01redhat
redhatrhacm2/console-rhel9:17873351052026-08-26redhat
redhatrhacm2/console-rhel9:17873392492026-08-26redhat
redhatrhacm2/console-rhel9:17876870622026-08-26redhat
redhatrhacm2/console-rhel9:17873392482026-08-26redhat
redhatmulticluster-engine/console-mce-rhel9:17870793592026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17866688562026-08-25redhat
redhatopenshift4/ose-console-rhel9:17871583412026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17872642502026-08-25redhat
redhatmulticluster-engine/console-mce-rhel9:17872590482026-08-25redhat
redhatrhacm2/console-rhel9:17869083612026-08-19redhat
redhatmulticluster-engine/console-mce-rhel9:17869119772026-08-19redhat
redhatansible-automation-platform/automation-portal:17870471142026-08-18redhat
redhatansible-automation-platform/automation-portal:17870471882026-08-18redhat
redhatprometheus3-5-main-3.5.5-0.8.hum12026-08-13redhat
redhatdiscovery/discovery-ui-rhel9:17866348252026-08-13redhat
redhatgrafana12-4-main-12.4.8-0.1.1.hum12026-08-13redhat
redhatgrafana13-1-main-13.1.3-0.1.hum12026-08-12redhat
redhatprometheus3-13-main-3.13.2-0.2.hum12026-08-04redhat
redhatjaeger-main-2.20.0-0.8.hum12026-07-30redhat

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

(7 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFixed inDependents
node-mocha9.1.4+ds1+~cs28.2.8-1
node-postcss8.4.20+~cs8.0.23-1 ... 8.5.9+~cs9.3.30-1 (18 versions)
Debian:13(2)
PackageVulnerable rangeFixed inDependents
node-mocha9.1.4+ds1+~cs28.2.8-1
node-postcss8.4.49+~cs9.2.32-1 ... 8.5.9+~cs9.3.30-1 (14 versions)
Debian:14(2)
PackageVulnerable rangeFixed inDependents
node-mocha9.1.4+ds1+~cs28.2.8-1
node-postcss8.4.49+~cs9.2.32-1, 8.5.12+~cs9.3.32-1, 8.5.6+~cs9.3.28-1, 8.5.8+~cs9.3.30-1, 8.5.9+~cs9.3.30-18.5.14+~cs9.3.34-1
npm(1)
PackageVulnerable rangeFixed inDependents
nanoid5.1.11

Weakness Classification(1)

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

Additional Vendor Advisories

(9)

Data Freshness Timeline

(refreshed 24× in last 7d / 105× 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 141 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-73086?
CVE-2026-73086 is a high vulnerability published on August 11, 2026. nanoid is a secure, URL-friendly, unique string ID generator for JavaScript. Prior to versions 3.3.12 and 5.1.11, the nanoid(size) function in index.js and index.cjs coerces the user-influenced size parameter to a signed 32-bit integer, allowing a value of 2147483648 to become -2147483648 and…
When was CVE-2026-73086 disclosed?
CVE-2026-73086 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-73086 actively exploited?
CVE-2026-73086 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 77.5% of all scored CVEs.
What is the CVSS score of CVE-2026-73086?
CVE-2026-73086 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-73086?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-73086, 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-73086

Explore →

Is Your Infrastructure Affected by CVE-2026-73086?

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