# CVE-2026-44697: Klever-Go MultiDataInterceptor: remote OOM via crafted compressed P2P payload


- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 29 May 2026
- **Updated:** 21 Jul 2026
- **Also known as:** GHSA-87m7-qffr-542v, GO-2026-5246

## What is CVE-2026-44697?

CVE-2026-44697 is a high-severity vulnerability in klever-io klever-go, published on 29 May 2026. 

### Official 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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-409 (Improper Handling of Highly Compressed Data (Data Amplification))

## Which versions are affected by CVE-2026-44697?

3 open source packages ship an affected version, including github.com/klever-io/klever-go.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/klever-io/klever-go` | Go | All versions | None |
| `github.com/klever-io/klever-go` | Go | All versions to 1.7.16 | None |
| `github.com/klever-io/klever-go` | Go | All versions to 1.7.16 | None |

## How do I fix CVE-2026-44697?

Upgrade to a fixed version.

## Is CVE-2026-44697 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44697 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44697 and fix it if it is affected.

What it is: CVE-2026-44697 is a high-severity vulnerability in klever-io klever-go, published on 29 May 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44697 exists.

Affected packages and fixed versions:
- github.com/klever-io/klever-go (Go): affected all versions; no fix listed
- github.com/klever-io/klever-go (Go): affected all versions up to 1.7.16; no fix listed
- github.com/klever-io/klever-go (Go): affected all versions up to 1.7.16; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44697/ (Markdown: https://insights.sbomify.com/CVE-2026-44697/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44697
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44697
- OSV: https://osv.dev/vulnerability/CVE-2026-44697

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44697/
Summaries are generated and may contain mistakes; the official description above is the record.