---
id: CVE-2026-52878
title: Klever-Go is the Go implementation of the Klever blockchain protocol
summary: >-
  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 c…
severity: high
cvss: 7.5
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'
cwe:
  - CWE-476
published: '2026-08-07'
updated: '2026-09-09'
sourceUpdated: '2026-09-09T20:55:04.493'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-52878'
references:
  - url: 'https://github.com/klever-io/klever-go/releases/tag/v1.7.18'
    label: security-advisories@github.com
  - url: >-
      https://github.com/klever-io/klever-go/security/advisories/GHSA-rm5c-5x2p-48wr
    label: security-advisories@github.com
  - url: >-
      https://github.com/klever-io/klever-go/security/advisories/GHSA-rm5c-5x2p-48wr
    label: 134c704f-9b21-4f2e-91b3-4a467353bcc0
tags:
  - nvd
epss: 0.00337
epssPercentile: 0.27221
ingestedAt: '2026-09-09T21:22:45.526Z'
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.