# CVE-2026-52879: klever-go: Unbounded goroutine spawn on direct-message ingress enables peer-driven DoS

Source: https://junglewise.ai/threats/cve-2026-52879-klever-go-unbounded-goroutine-spawn-on-direct-message-ingress  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-07  
License: CC BY 4.0 with a link back

CVE-2026-52879 · Severity: high · CVSS 7.5 · Published 2026-08-07

Klever-Go is the Go implementation of the Klever blockchain protocol. In versions 1.7.14 through 1.7.17, the direct-message ingress handler spawns a new goroutine for every incoming direct message before the processor-level antiflood layer makes any admission decision, with no semaphore, throttler, or bound on the number of concurrent in-flight spawns. Because the antiflood check runs inside the spawned goroutine rather than before it, a single connected peer can open a direct-send stream and send a stream of well-formed messages to force unbounded goroutine creation, where each goroutine allocates its own stack and holds a message reference until processing completes, adding scheduler and garbage-collection pressure faster than the runtime can drain it. This lets one peer degrade the node's availability and its ability to process legitimate traffic, resulting in a remotely triggerable denial of service. The issue is fixed in 1.7.18.

Technologies: [github.com/klever-io/klever-go (Go)](https://junglewise.ai/threats/technologies/github-com-klever-io-klever-go). Vendors: [Go](https://junglewise.ai/threats/vendors/go).

## Quick answers

**Is CVE-2026-52879 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-52879 being exploited in the wild.

**How severe is CVE-2026-52879?** High severity, with a CVSS score of 7.5, published 7 August 2026.

**Which products and versions are affected?** github.com/klever-io/klever-go (Go) SEMVER:introduced=1.7.14,fixed=1.7.18.

**Is there a fix for CVE-2026-52879?** Yes. github.com/klever-io/klever-go (Go): upgrade to 1.7.18 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2026-52879?** Check whether you run github.com/klever-io/klever-go (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/klever-io/klever-go (Go): upgrade to 1.7.18 or later

  ```sh
  go get github.com/klever-io/klever-go@v1.7.18
  ```


## Affected products

- github.com/klever-io/klever-go (Go) SEMVER:introduced=1.7.14,fixed=1.7.18

## Identifiers

- CVE-2026-52879
- GHSA-hf2g-6j7h-98wg
- GO-2026-5424

## Related threats

- [Klever-Go unauthenticated WebSocket /subscribe remote DoS](https://junglewise.ai/threats/cve-2026-86065-klever-go-unauthenticated-websocket-subscribe-remote-dos)
- [Klever-Go /log endpoint unauthenticated logging configuration manipulation](https://junglewise.ai/threats/cve-2026-86064-klever-go-log-endpoint-unauthenticated-logging-configuration)
- [Klever-Go Elasticsearch injection via account name](https://junglewise.ai/threats/cve-2026-82409-klever-go-elasticsearch-injection-via-account-name)
- [Klever-Go BLS public key validation bypass in validator registration](https://junglewise.ai/threats/cve-2026-82407-klever-go-bls-public-key-validation-bypass-in-validator)
- [Klever-Go marketplace Buy missing IsClaimed guard](https://junglewise.ai/threats/cve-2026-82406-klever-go-marketplace-buy-missing-isclaimed-guard)