# CVE-2026-86064: Klever-Go: /log controls global node logging

> Unauthenticated remote attackers can modify global log settings and access live process logs via the /log WebSocket route in Klever-Go nodes.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-9v8p-frvj-2pcm, GO-2026-6583

## What is CVE-2026-86064?

CVE-2026-86064 is a high-severity missing authorization vulnerability in klever-io klever-go, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-86064?

3 open source packages ship an affected version, including github.com/klever-io/klever-go.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/klever-io/klever-go` | Go | All versions | 1.7.20 |
| `github.com/klever-io/klever-go` | Go | All versions | 1.7.20 |
| `github.com/klever-io/klever-go` | Go | All versions | 1.7.20 |

## How do I fix CVE-2026-86064?

Upgrade github.com/klever-io/klever-go to 1.7.20 or later.

## Is CVE-2026-86064 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86064 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86064 and fix it if it is affected.

What it is: CVE-2026-86064 is a high-severity missing authorization vulnerability in klever-io klever-go, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86064 exists.

Affected packages and fixed versions:
- github.com/klever-io/klever-go (Go): affected all versions; fixed in 1.7.20
- github.com/klever-io/klever-go (Go): affected all versions; fixed in 1.7.20
- github.com/klever-io/klever-go (Go): affected all versions; fixed in 1.7.20

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-86064/ (Markdown: https://insights.sbomify.com/CVE-2026-86064/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-86064
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-86064
- OSV: https://osv.dev/vulnerability/CVE-2026-86064

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-86064/
Summaries are generated and may contain mistakes; the official description above is the record.