CVE-2026-52878
- Source
- https://cve.org/CVERecord?id=CVE-2026-52878
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-52878.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-52878
- Aliases
- Downstream
- Related
- Published
- 2026-08-07T22:32:27.340Z
- Modified
- 2026-08-08T11:46:25.703572388Z
- Severity
-
- 7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- Klever-Go: Unauthenticated nil-pointer DoS in P2P transaction validation can halt the chain
- Details
-
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.
- Database specific
{ "cwe_ids": [ "CWE-476" ], "cna_assigner": "GitHub_M", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/52xxx/CVE-2026-52878.json" }- References