CVE-2026-86065 Klever-Go: Unauthenticated WebSocket /subscribe: no read-size limit, no connection cap, permissive origin -> remote node memory/goroutine exhaustion (DoS)

High 7.5 Published Updated

Unauthenticated WebSocket connections in Klever-Go allow remote attackers to exhaust node memory and goroutines, causing a denial of service.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-86065?

CVE-2026-86065 is a high-severity denial of service 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 /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.

Weakness: CWE-770

Which versions are affected by CVE-2026-86065?

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

PackageAffectedFixed in
github.com/klever-io/klever-go GoAll versions1.7.20
github.com/klever-io/klever-go GoAll versions1.7.20
github.com/klever-io/klever-go GoAll versions1.7.20

How do I fix CVE-2026-86065?

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

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is CVE-2026-86065 being exploited?

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

Sources

Also known as GHSA-4fwh-wrm6-97xm, GO-2026-6581.

Is CVE-2026-86065 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free