CVE-2026-52879: CWE-400: Uncontrolled Resource Consumption in klever-io klever-go
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.
AI Analysis
Technical Summary
Klever-Go, the Go implementation of the Klever blockchain protocol, has an uncontrolled resource consumption vulnerability (CWE-400) in versions 1.7.14 through 1.7.17. The direct-message ingress handler spawns a new goroutine for each incoming direct message before the antiflood admission control runs, with no concurrency limits. Because the antiflood check occurs inside the spawned goroutine rather than before it, a single connected peer can send a continuous stream of messages that cause unbounded goroutine creation. Each goroutine allocates stack memory and holds message references until processing completes, increasing scheduler and garbage collection pressure beyond what the runtime can handle. This results in degraded node availability and denial of service. The vulnerability is fixed in version 1.7.18.
Potential Impact
An attacker controlling a single peer can remotely trigger a denial of service by causing the node to spawn an unbounded number of goroutines, exhausting system resources. This degrades the node's availability and its ability to process legitimate traffic. There is no impact on confidentiality or integrity reported.
Mitigation Recommendations
Upgrade Klever-Go to version 1.7.18 or later, where this issue is fixed. No other mitigation or temporary workaround is indicated in the provided data.
CVE-2026-52879: CWE-400: Uncontrolled Resource Consumption in klever-io klever-go
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.
CVSS v3.1
Score 7.5high
Affected software
pkg:golang/github.com/klever-io/klever-goRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Klever-Go, the Go implementation of the Klever blockchain protocol, has an uncontrolled resource consumption vulnerability (CWE-400) in versions 1.7.14 through 1.7.17. The direct-message ingress handler spawns a new goroutine for each incoming direct message before the antiflood admission control runs, with no concurrency limits. Because the antiflood check occurs inside the spawned goroutine rather than before it, a single connected peer can send a continuous stream of messages that cause unbounded goroutine creation. Each goroutine allocates stack memory and holds message references until processing completes, increasing scheduler and garbage collection pressure beyond what the runtime can handle. This results in degraded node availability and denial of service. The vulnerability is fixed in version 1.7.18.
Potential Impact
An attacker controlling a single peer can remotely trigger a denial of service by causing the node to spawn an unbounded number of goroutines, exhausting system resources. This degrades the node's availability and its ability to process legitimate traffic. There is no impact on confidentiality or integrity reported.
Mitigation Recommendations
Upgrade Klever-Go to version 1.7.18 or later, where this issue is fixed. No other mitigation or temporary workaround is indicated in the provided data.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-08T21:44:27.364Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a765f31bf8831d5394839e4
Added to database: 08/07/2026, 22:41:53 UTC
Last enriched: 08/15/2026, 15:33:03 UTC
Last updated: 09/08/2026, 10:52:10 UTC
Views: 56
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.