Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, the default-open GET /log WebSocket route configured in config/node/api.yaml and registered by network/api/api.go does not require authentication. The first client message is parsed as a logger Profile in network/api/logs/logSender.go and applied process-wide through Profile.Apply, allowing a remote client to change global log levels and formatting options until the connection closes. The same connection is registered as a log observer and can receive live process logs. An attacker can suppress normal logs, increase verbosity, distort operator visibility, and access operational information without credentials. This issue is fixed in version 1.7.20.
CVE-2026-86064
HIGHPre-NVD 8.68.6—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 8.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 69% 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
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.6Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.6
- EG Score
- 8.6(medium)
- EG Risk
- 70(Attend)EG Risk 70/100SSVC: Attend
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 computedSeverity86% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 31%
- KEV
- Not listed
Published
September 23, 2026
Last Modified
September 23, 2026
Advisory Details (4)
Auto-updated Sep 23, 2026🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
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.20github_commit Patch Available
commit a2740c985a78 (klever-io/klever-go)
Patch available: klever-io/klever-go v1.7.20 (contains commit a2740c985a78)
https://github.com/klever-io/klever-go/commit/a2740c985a788fb69e17742ea4f0c37c440733b2github_pr Patch Available
[KLC-2438] require auth for /log and stop unauthenticated logger mutation (GHSA-9v8p-frvj-2pcm)
Patch available: klever-io/klever-go v1.7.20 (PR #74 merged 2026-07-01)
https://github.com/klever-io/klever-go/pull/74github Patch Available🟡 PoC Available
/log controls global node logging · Advisory · klever-io/klever-go · GitHub
https://github.com/klever-io/klever-go/security/advisories/GHSA-9v8p-frvj-2pcmVendor Advisories for CVE-2026-86064(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/klever-io/klever-go | — | 1.7.20 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× 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.
- 2026-09-24 18:57 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 20:22 UTCEG score recompute
- 2026-09-23 19:39 UTCEG score recompute
- 2026-09-23 19:19 UTCEG score recompute
- 2026-09-23 19:19 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownGo:github.com/klever-io/klever-go
Frequently asked(5)
What is CVE-2026-86064?
CVE-2026-86064 is a high vulnerability 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 /log WebSocket route configured in config/node/api.yaml and registered by network/api/api.go does not require authentication. The first client message is parsed as a logger Profile in…
When was CVE-2026-86064 disclosed?
CVE-2026-86064 was first published in the National Vulnerability Database on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-86064 actively exploited?
CVE-2026-86064 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 68.9% of all scored CVEs.
What is the CVSS score of CVE-2026-86064?
CVE-2026-86064 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-86064?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-86064, 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-86064
Is Your Infrastructure Affected by CVE-2026-86064?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.