CVE-2026-52879

Klever-Go: Unbounded goroutine spawn on direct-message ingress enables peer-driven DoS

Published Aug 7, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The flaw in Klever-Go allows a connected peer to send a stream of well‑formed direct messages that causes the node to spawn a new goroutine for each message before any antiflood checks are applied. Each goroutine allocates its own stack and retains a reference to the message until processing finishes, creating unbounded resource consumption and increasing scheduler and garbage‑collection pressure. The result is a remotely triggerable denial of service that degrades the node’s availability and its ability to process legitimate traffic.

Affected Systems

Klever‑IO’s Klever-Go blockchain implementation is affected for all releases from 1.7.14 through 1.7.17. The vulnerability is fixed in version 1.7.18; no other vendors or products are impacted.

Risk and Exploitability

The CVSS score of 7.5 indicates a high severity risk, and although an EPSS score is not available, the flaw is not listed in CISA’s KEV catalog. A single connected peer can, by opening a direct‑send stream, flood the node with messages and trigger unbounded goroutine creation. The lack of throttling or a semaphore means the attack does not require special privileges, making the vector likely to be any external peer that can reach the node’s ingress interface.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Klever-Go to version 1.7.18 or later to apply the vendor fix.
  • If an upgrade is delayed, apply network‑level rate limiting or firewall rules to constrain the number of direct‑message connections a single peer can establish.
  • Consider temporarily disabling direct‑message ingress or isolating the node until the patch is deployed to prevent the resource exhaustion attack from occurring.

Generated by OpenCVE AI on August 7, 2026 at 23:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-hf2g-6j7h-98wg klever-go: Unbounded goroutine spawn on direct-message ingress enables peer-driven DoS
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Klever-io
Klever-io klever-go
Vendors & Products Klever-io
Klever-io klever-go
Type Values Removed Values Added
Description 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.
Title Klever-Go: Unbounded goroutine spawn on direct-message ingress enables peer-driven DoS
Weaknesses CWE-400
CWE-770
References
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-770

    Allocation of Resources Without Limits or Throttling

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 10, 2026, 1:36 PM
Reserved
Jun 8, 2026, 9:44 PM
Status
Deferred
Published
Aug 7, 2026, 11:17 PM
Modified
Oct 24, 2026, 4:10 PM