CVE-2026-58262

Klever-Go: PubKeysBitmap padding bits bypass the BLS signature quorum

Published Aug 7, 2026 CVSS 4.0 · 7.1 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability allows a block producer to set unused padding bits in the PubKeysBitmap field so that they count toward the BLS signature quorum. Because those padding bits do not correspond to any real validator, the aggregate‑signature verification still succeeds while the actual quorum of genuine validator signatures is lower than required. Nodes that accept such a header believe the block has a valid two‑thirds quorum, thereby weakening consensus safety and undermining finality.

Affected Systems

Klever‑Go, the Go implementation of the Klever blockchain protocol. All releases before version 1.7.20 are vulnerable. Versions 1.7.20 and later have fixed the counting of padding bits.

Risk and Exploitability

The CVSS score of 7.1 indicates a high severity vulnerability with no known mitigations beyond the fix. The EPSS score is not available, and the vulnerability is not listed in CISA’s KEV catalog, but its impact on blockchain consensus makes it critical for operators. A malicious or compromised block producer can craft a header with padding bits that inflate the quorum, allowing them to overstate validator participation and potentially forge blocks. Verification of the padding bits is required to restore proper quorum enforcement.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Klever-Go to version 1.7.20 or later to apply the official fix that corrects PubKeysBitmap quorum counting.
  • Manually isolate or temporarily suspend any unpatched nodes from participating in block validation until the update is applied, preventing them from influencing consensus.
  • Deploy monitoring to detect block headers containing excessive padding bits and reject them from propagation.

Generated by OpenCVE AI on August 8, 2026 at 00:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Klever-io
Klever-io klever-go
Vendors & Products Klever-io
Klever-io klever-go
Type Values Removed Values Added
Description 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.
Title Klever-Go: PubKeysBitmap padding bits bypass the BLS signature quorum
Weaknesses CWE-345
CWE-347
References
Metrics cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

  • CWE-347

    Improper Verification of Cryptographic Signature

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 12, 2026, 10:15 PM
Reserved
Jun 29, 2026, 9:54 PM
Status
Deferred
Published
Aug 7, 2026, 10:16 PM
Modified
Oct 24, 2026, 4:10 PM