CVE-2026-44697: Klever-Go MultiDataInterceptor: remote OOM via crafted compressed P2P payload
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.
Security readout for executives and security teams
Plain-English summary
Klever-Go nodes before 1.7.17 can be crashed remotely by a very small crafted compressed P2P message that expands into extreme memory use. For validators, this can cause outages; across many nodes, it can affect chain liveness. The source bundle names a fixed version: 1.7.17.
Executive priority
Treat as urgent for Klever validator or infrastructure operators. The issue affects availability, requires no authentication, and can disrupt validator service from a small network payload.
Technical view
The vulnerability is in Batch.Decompress in data/batch/batch.go, reached through topics served by MultiDataInterceptor. A remote unauthenticated peer can trigger multi-gigabyte heap allocation from a sub-50 KiB gossip payload, causing denial of service. CVSS is 8.6, with CWE-409 and CWE-770 mapped.
Likely exposure
Klever blockchain nodes running klever-go versions earlier than 1.7.17 are exposed, especially validators and peers participating in MultiDataInterceptor-served P2P topics.
Exploitation context
The bundle states a single packet can OOM-kill a conventionally provisioned validator. It does not cite KEV listing or active exploitation evidence, so active exploitation is not established here.
Researcher notes
Evidence is limited to the CVE record, CVE List entry, and GitHub advisory reference in the bundle. The named fix is 1.7.17. No exploit code, public exploitation claim, or additional mitigation detail is provided here.
Mitigation direction
Upgrade klever-go to version 1.7.17 or later.
Prioritize validators and publicly reachable P2P nodes for rollout.
Review the GitHub advisory for any updated vendor guidance.
Monitor node memory, restarts, and validator availability during rollout.
Validation and detection
Inventory all klever-go nodes and record running versions.
Confirm no production node remains on a version earlier than 1.7.17.
Check validator and peer logs for recent OOM kills or unexplained restarts.
Verify upgraded nodes are running the intended fixed binary.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-409: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.