CVE-2026-86065

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-23. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-85575 (ENISA EUVD) · GHSA-4fwh-wrm6-97xm (GitHub Security Advisories) · GO-2026-6581 (OSV.dev)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, the default-open GET /subscribe endpoint in network/api/websocket/routes.go accepts unauthenticated WebSocket clients with permissive origin handling, does not call SetReadLimit to bound message size, and has no live-connection cap. SocketHub.HandleClientInsertion also accepts an unbounded address list that grows addressSubscription, and client.loopIn continues reading without a size limit, allowing one client to grow subscription maps or many clients to retain goroutines, buffered channels, and descriptors. The global HTTP request throttler does not count upgraded live WebSocket connections. Because the REST and WebSocket API runs in the node process, memory or scheduler exhaustion can crash the node and interrupt P2P and consensus participation. This issue is fixed in version 1.7.20.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 23, 2026

Last Modified

September 29, 2026

Advisory Details (4)

Auto-updated Sep 23, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
GitHub release Patch Available

v1.7.20 - CertiK Audit Remediation & Coordinated Security Release

Patch available: klever-io/klever-go v1.7.20

https://github.com/klever-io/klever-go/releases/tag/v1.7.20
GitHub commit Patch Available

commit b8af922e749e (klever-io/klever-go)

Patch available: klever-io/klever-go v1.7.20 (contains commit b8af922e749e)

https://github.com/klever-io/klever-go/commit/b8af922e749ec1fa7451b2c6e7c9f634d8603be2
GitHub pull request Patch Available

[KLC-2440] Bound /subscribe WebSocket reads, connections, and subscriptions (GHSA-4fwh-wrm6-97xm)

Patch available: klever-io/klever-go v1.7.20 (PR #76 merged 2026-07-03)

https://github.com/klever-io/klever-go/pull/76
GitHub advisoryMentions a patch (unverified)

Unauthenticated WebSocket /subscribe: no read-size limit, no connection cap, permissive origin -> remote node memory/goroutine exhaustion (DoS) · Advisory · klever-io/klever-go · GitHub

https://github.com/klever-io/klever-go/security/advisories/GHSA-4fwh-wrm6-97xm

Vendor Advisories for CVE-2026-86065(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/klever-io/klever-go @ 1.7.20 (fixes < 1.7.20)—ghsa

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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/klever-io/klever-go—
  • every version up to 1.7.20: fixed in 1.7.20
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 49× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-11-01 07:38 UTCGHSA enrichmentGHSA-4fwh-wrm6-97xm · GitHub severity HIGH · GitHub CVSS 7.5
  3. 2026-11-01 07:38 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  6. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  7. 2026-10-28 21:40 UTCEG score recompute
  8. 2026-10-28 18:55 UTCOSV refresh
  9. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-10-25 13:55 UTCEG score recompute
  14. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  17. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  18. 2026-10-20 21:24 UTCEG score recompute
  19. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  20. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  21. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  22. 2026-10-18 03:05 UTCEG score recompute
  23. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  24. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 27th percentile
  25. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 27th percentile
Show 45 more
  1. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  2. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  3. 2026-10-13 05:23 UTCEG score recompute
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  5. 2026-10-12 14:52 UTCEG score recompute
  6. 2026-10-11 19:17 UTCEG score recompute
  7. 2026-10-11 16:34 UTCEG score recompute
  8. 2026-10-11 13:51 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  10. 2026-10-10 22:18 UTCEG score recompute
  11. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  12. 2026-10-09 23:53 UTCEG score recompute
  13. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  14. 2026-10-08 23:11 UTCEG score recompute
  15. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  16. 2026-10-08 00:48 UTCEG score recompute
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  18. 2026-10-07 02:13 UTCEG score recompute
  19. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  20. 2026-10-06 03:49 UTCEG score recompute
  21. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  22. 2026-10-05 05:21 UTCEG score recompute
  23. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  24. 2026-10-03 19:45 UTCEG score recompute
  25. 2026-10-02 21:17 UTCEG score recompute
  26. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  27. 2026-10-01 22:51 UTCEG score recompute
  28. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  29. 2026-10-01 00:26 UTCEG score recompute
  30. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  31. 2026-09-30 01:58 UTCEG score recompute
  32. 2026-09-29 03:33 UTCEG score recompute
  33. 2026-09-29 02:36 UTCEG score recompute
  34. 2026-09-28 23:31 UTCEG score recompute
  35. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  36. 2026-09-27 13:57 UTCEG score recompute
  37. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  38. 2026-09-27 02:44 UTCEG score recompute
  39. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 26th percentile
  40. 2026-09-26 04:21 UTCEG score recompute
  41. 2026-09-24 18:45 UTCEG score recompute
  42. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.4% · 25th percentile
  43. 2026-09-23 20:22 UTCEG score recompute
  44. 2026-09-23 19:19 UTCEG score recomputeFirst assessed: 7.5 HIGH
  45. 2026-09-23 19:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-86065?
CVE-2026-86065 is a high-severity vulnerability; its CVE record was published on September 23, 2026. Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, the default-open GET /subscribe endpoint in network/api/websocket/routes.go accepts unauthenticated WebSocket clients with permissive origin handling, does not call SetReadLimit to bound message size, and has no…
When was the CVE record for CVE-2026-86065 published?
The CVE record for CVE-2026-86065 was published on September 23, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 29, 2026; the record at its source may have been updated since.
Is CVE-2026-86065 actively exploited?
CVE-2026-86065 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-86065?
CVE-2026-86065 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-86065?
A fix for CVE-2026-86065 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-86065 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-86065

Explore →

Is Your Infrastructure Affected by CVE-2026-86065?

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