---
id: CVE-2026-58262
title: Klever-Go is the Go implementation of the Klever blockchain protocol
summary: >-
  Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to
  1.7.20, header signature verification counts the unused padding bits of the
  PubKeysBitmap toward the two-thirds validator quorum. These padding bits do
  not co…
severity: none
cwe:
  - CWE-345
  - CWE-347
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-58262'
references:
  - url: >-
      https://github.com/klever-io/klever-go/commit/a11cb28e495e608d8034dbe83a91e89d0c68e0f7
    label: security-advisories@github.com
  - url: >-
      https://github.com/klever-io/klever-go/security/advisories/GHSA-f9h7-4mmq-vgcq
    label: security-advisories@github.com
tags:
  - nvd
epss: 0.00118
epssPercentile: 0.01937
ingestedAt: '2026-09-09T21:22:45.525Z'
---

## Overview

Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, header signature verification counts the unused padding bits of the PubKeysBitmap toward the two-thirds validator quorum. These padding bits do not correspond to any validator and are ignored by the actual BLS aggregate-signature check, so a malicious or compromised block producer can set them to reach the required quorum while gathering fewer genuine validator signatures than the protocol demands. As a result, nodes that import or intercept the header accept it as correctly signed without a real two-thirds quorum, weakening consensus safety and undermining finality. This issue is fixed in version 1.7.20.

## Remediation

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