---
id: CVE-2026-52879
title: Klever-Go is the Go implementation of the Klever blockchain protocol
summary: >-
  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 lay…
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'
cwe:
  - CWE-400
  - CWE-770
published: '2026-08-07'
updated: '2026-09-09'
sourceUpdated: '2026-09-09T20:55:04.493'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-52879'
references:
  - url: 'https://github.com/klever-io/klever-go/releases/tag/v1.7.18'
    label: security-advisories@github.com
  - url: >-
      https://github.com/klever-io/klever-go/security/advisories/GHSA-hf2g-6j7h-98wg
    label: security-advisories@github.com
  - url: >-
      https://github.com/klever-io/klever-go/security/advisories/GHSA-hf2g-6j7h-98wg
    label: 134c704f-9b21-4f2e-91b3-4a467353bcc0
tags:
  - nvd
epss: 0.00349
epssPercentile: 0.28583
ingestedAt: '2026-09-09T21:22:45.526Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.