CVE-2026-86064
Klever-Go is the Go implementation of the Klever blockchain …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/klever-io/klever-go/commit/a2740c985a788fb69e17742ea4f0c37c440733b2
- github.com/klever-io/klever-go/pull/74
- github.com/klever-io/klever-go/releases/tag/v1.7.20
- github.com/klever-io/klever-go/security/advisories/GHSA-9v8p-frvj-2pcm
- github.com/advisories/GHSA-9v8p-frvj-2pcm
- nvd.nist.gov/vuln/detail/CVE-2026-86064
- cve.org/CVERecord?id=CVE-2026-86064
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.