Skip to main content
VulnerabilityPublished Updated

CVE-2026-52878: klever-go · NULL Pointer Dereference

Affects klever-goSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 1.7.18 soon.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.7.18
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade klever-go and github.com/klever-io/klever-go to 1.7.18.

Affected software

ProductAffectedFixed in
klever-ioklever-goAffected
  • >=1.7.14 <1.7.18
Fixed in
  • 1.7.18
Gogithub.com/klever-io/klever-gopkg:golang/github.com/klever-io/klever-goOther threatsAffected
  • <1.7.18 >=1.7.14
Fixed in
  • 1.7.18

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Klever-Go version 1.7.18. Users and operators should upgrade to version 1.7.18 or later to remediate this vulnerability. Until upgraded, nodes remain vulnerable to denial-of-service attacks via malformed protobuf transactions. No other mitigations are documented.

Description

Klever-Go is the Go implementation of the Klever blockchain protocol. Versions 1.7.14 through 1.7.17 are vulnerable to a nil-pointer panic triggered by a protobuf Transaction whose embedded RawData sub-message is omitted. This omission causes RawData to decode to nil. Every transaction gossiped on the Klever-Go P2P network is decoded and validated synchronously inside the libp2p pubsub topic-validator callback, where txVersionChecker.CheckTxVersion dereferences tx.RawData.Version with no nil check. Because the libp2p pubsub callback, the underlying go-libp2p-pubsub validation worker, and Klever's own network/p2p layer install no recover(), the panic propagates and crashes the entire node process. The attacker payload is a 3-byte protobuf message; no validator key, stake, funds, or on-chain account is required, and delivery aimed at enough of the BLS validator set can halt block production, resulting in a chain halt. This issue has been fixed in version 1.7.18.

References

Community reviews

Loading reviews…