Vulnerability 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.
CVSS Score
HIGH
Related Weaknesses (CWE)
References
- https://github.com/klever-io/klever-go/releases/tag/v1.7.18
- https://github.com/klever-io/klever-go/security/advisories/GHSA-rm5c-5x2p-48wr
FAQ
What is CVE-2026-52878?
CVE-2026-52878 is a vulnerability with a CVSS score of 7.5 (HIGH). 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 su...
How severe is CVE-2026-52878?
CVE-2026-52878 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-52878?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.