CVE-2026-44697
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedKlever-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA decompression bomb vulnerability in Klever-Go's Batch.Decompress allows remote, unauthenticated attackers to send a sub-50 KiB compressed payload that expands to multi-gigabyte sizes in memory upon decompression, causing immediate OOM (Out of Memory) crashes on receiving validator nodes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Klever-Go is runningCheck running processes for klever-go binary, or inspect node logs for Klever-Go startup messagesAffected if Klever-Go node is running as a validator or full node
-
Check installed Klever-Go versionRun 'klever-go --version' or check node logs for version string at startup, then compare to 1.7.17Affected if Version is earlier than 1.7.17 (v1.7.0 through v1.7.16 are affected)
-
Verify MultiDataInterceptor topic is enabledInspect node configuration files (config.toml or similar) for MultiDataInterceptor or pubsub topic settingsAffected if MultiDataInterceptor topic subscription is enabled in the node config
-
Check for abnormal memory allocation patternsMonitor node memory usage; look for sudden multi-gigabyte heap allocation spikes in metrics or logs after receiving gossipAffected if Node exhibits unexplained OOM events or memory spikes correlating with gossip reception on MultiDataInterceptor
A node is affected if running Klever-Go version before 1.7.17 with MultiDataInterceptor enabled, and showing abnormal memory behavior under gossip load.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Klever-Go to version 1.7.17 or later which contains the fix. Consider network-level rate limiting on the MultiDataInterceptor topic as an interim defense.
Klever-Go version 1.7.17 or later
- Identify the current Klever-Go version running in your environment (check via binary version flag or deployment configuration)
- Upgrade Klever-Go to version 1.7.17 or later
- Restart the affected node(s) to apply the new binary
- Verify the upgrade was successful by checking the running version
- Monitor node memory usage to confirm the DoS vulnerability is mitigated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44697 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-44697 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data