CVE-2026-47249: CWE-400: Uncontrolled Resource Consumption in klever-io klever-go
Klever-Go prior to version 1.7.18 contains a vulnerability in its P2P resolver request handling logic that allows a connected peer to send a compressed request which expands into a large number of decoded hash entries. This leads to uncontrolled resource consumption due to the resolver preallocating and iterating over an unchecked large set of hashes, causing memory and CPU amplification. The issue is fixed in version 1.7.18.
AI Analysis
Technical Summary
Klever-Go, the Go implementation of the Klever blockchain protocol, has a vulnerability (CVE-2026-47249) in versions before 1.7.18 where the P2P resolver request handling logic is susceptible to hash-array amplification. A compressed RequestDataType_HashArrayType request of only 442 bytes can decompress into 200,000 hash entries. The antiflood logic counts only the compressed message size and a single logical message, but does not limit the number of decoded repeated-field items. Consequently, TxResolver and TrieNodeResolver preallocate and process the entire large set of decoded hashes, resulting in remote memory and CPU resource exhaustion for nodes accepting P2P connections. This vulnerability is classified under CWE-400 (Uncontrolled Resource Consumption).
Potential Impact
An attacker can cause a denial of service by sending a specially crafted compressed request that expands into a very large number of hash entries, leading to excessive memory allocation and CPU usage on the targeted node. This can degrade or disrupt the availability of the affected Klever-Go node. There is no impact on confidentiality or integrity according to the CVSS vector. No known exploits in the wild have been reported.
Mitigation Recommendations
This vulnerability is fixed in Klever-Go version 1.7.18. Users should upgrade to version 1.7.18 or later to remediate this issue. No other mitigation or temporary workaround is indicated. Patch status is not explicitly confirmed in vendor advisories but the fix version is clearly stated.
CVE-2026-47249: CWE-400: Uncontrolled Resource Consumption in klever-io klever-go
Description
Klever-Go prior to version 1.7.18 contains a vulnerability in its P2P resolver request handling logic that allows a connected peer to send a compressed request which expands into a large number of decoded hash entries. This leads to uncontrolled resource consumption due to the resolver preallocating and iterating over an unchecked large set of hashes, causing memory and CPU amplification. The issue is fixed in version 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.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Klever-Go, the Go implementation of the Klever blockchain protocol, has a vulnerability (CVE-2026-47249) in versions before 1.7.18 where the P2P resolver request handling logic is susceptible to hash-array amplification. A compressed RequestDataType_HashArrayType request of only 442 bytes can decompress into 200,000 hash entries. The antiflood logic counts only the compressed message size and a single logical message, but does not limit the number of decoded repeated-field items. Consequently, TxResolver and TrieNodeResolver preallocate and process the entire large set of decoded hashes, resulting in remote memory and CPU resource exhaustion for nodes accepting P2P connections. This vulnerability is classified under CWE-400 (Uncontrolled Resource Consumption).
Potential Impact
An attacker can cause a denial of service by sending a specially crafted compressed request that expands into a very large number of hash entries, leading to excessive memory allocation and CPU usage on the targeted node. This can degrade or disrupt the availability of the affected Klever-Go node. There is no impact on confidentiality or integrity according to the CVSS vector. No known exploits in the wild have been reported.
Mitigation Recommendations
This vulnerability is fixed in Klever-Go version 1.7.18. Users should upgrade to version 1.7.18 or later to remediate this issue. No other mitigation or temporary workaround is indicated. Patch status is not explicitly confirmed in vendor advisories but the fix version is clearly stated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-18T22:54:18.273Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a765bb3bf8831d539436f3c
Added to database: 08/07/2026, 22:26:59 UTC
Last enriched: 08/07/2026, 22:41:05 UTC
Last updated: 08/07/2026, 22:46:43 UTC
Views: 4
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.