CVE-2026-44697: CWE-409: Improper Handling of Highly Compressed Data (Data Amplification) in klever-io klever-go
Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.17, a remote, unauthenticated denial-of-service vulnerability in Batch.Decompress (data/batch/batch.go) allows any peer that participates in a topic served by MultiDataInterceptor to allocate multi-gigabyte heaps on the receiving node from a sub-50 KiB gossip payload. A single packet is sufficient to OOM-kill a validator with conventional memory provisioning. Fleet-wide application affects chain liveness. This vulnerability is fixed in 1.7.17.
AI Analysis
Technical Summary
CVE-2026-44697 is a high-severity denial-of-service vulnerability in klever-io's klever-go blockchain implementation. The flaw exists in the Batch.Decompress function (data/batch/batch.go) used by MultiDataInterceptor, where highly compressed data is improperly handled. An attacker can send a small compressed packet that expands into multi-gigabyte memory allocations on the receiving node, leading to OOM and process termination. This vulnerability requires no authentication and can be triggered remotely by any peer participating in the affected topic. The vulnerability impacts chain liveness by potentially crashing validator nodes fleet-wide. It is fixed in klever-go version 1.7.17.
Potential Impact
An unauthenticated remote attacker can cause a denial-of-service by sending a specially crafted small compressed packet that triggers excessive memory allocation on the target node. This leads to out-of-memory conditions and crashes the validator process, disrupting blockchain operations and affecting overall chain liveness.
Mitigation Recommendations
Upgrade klever-go to version 1.7.17 or later, where this vulnerability is fixed. No other mitigation or workaround is indicated. Patch status is confirmed by the vendor advisory stating the fix in 1.7.17.
CVE-2026-44697: CWE-409: Improper Handling of Highly Compressed Data (Data Amplification) in klever-io klever-go
Description
Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.17, a remote, unauthenticated denial-of-service vulnerability in Batch.Decompress (data/batch/batch.go) allows any peer that participates in a topic served by MultiDataInterceptor to allocate multi-gigabyte heaps on the receiving node from a sub-50 KiB gossip payload. A single packet is sufficient to OOM-kill a validator with conventional memory provisioning. Fleet-wide application affects chain liveness. This vulnerability is fixed in 1.7.17.
CVSS v3.1
Score 8.6high
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
CVE-2026-44697 is a high-severity denial-of-service vulnerability in klever-io's klever-go blockchain implementation. The flaw exists in the Batch.Decompress function (data/batch/batch.go) used by MultiDataInterceptor, where highly compressed data is improperly handled. An attacker can send a small compressed packet that expands into multi-gigabyte memory allocations on the receiving node, leading to OOM and process termination. This vulnerability requires no authentication and can be triggered remotely by any peer participating in the affected topic. The vulnerability impacts chain liveness by potentially crashing validator nodes fleet-wide. It is fixed in klever-go version 1.7.17.
Potential Impact
An unauthenticated remote attacker can cause a denial-of-service by sending a specially crafted small compressed packet that triggers excessive memory allocation on the target node. This leads to out-of-memory conditions and crashes the validator process, disrupting blockchain operations and affecting overall chain liveness.
Mitigation Recommendations
Upgrade klever-go to version 1.7.17 or later, where this vulnerability is fixed. No other mitigation or workaround is indicated. Patch status is confirmed by the vendor advisory stating the fix in 1.7.17.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-07T17:07:09.316Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a19cdf2e29bf47b50fb4701
Added to database: 05/29/2026, 17:33:38 UTC
Last enriched: 07/21/2026, 21:09:09 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 54
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.
External Links
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.