Live › vulnerability › CVE-2026-86064
Go to dashboardKlever-Go, the Go implementation of the Klever blockchain node, exposes an unauthenticated GET /log WebSocket route by default. A remote client can change the node's global log levels and formatting and read live process logs without credentials.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| github.com/klever-io/klever-go | go | < 1.7.20 | 1.7.20 |
Check config/node/api.yaml for the /log route being enabled, and confirm the node's API port is reachable from untrusted networks.
1.7.20 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-86064")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.