CVE-2026-58262: CWE-345: Insufficient Verification of Data Authenticity in klever-io klever-go
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.
AI Analysis
Technical Summary
Klever-Go, the Go implementation of the Klever blockchain protocol, improperly counts unused padding bits of the PubKeysBitmap as valid signatures toward the two-thirds validator quorum in versions before 1.7.20. These padding bits do not correspond to any validator and are ignored by the actual BLS aggregate-signature check. A malicious or compromised block producer can exploit this by setting padding bits to falsely reach quorum, causing nodes to accept headers without a real two-thirds quorum. This undermines consensus safety and finality. The vulnerability is addressed in version 1.7.20.
Potential Impact
The vulnerability allows a block producer to bypass the required two-thirds validator signature quorum by exploiting unused padding bits, leading to acceptance of improperly signed headers. This weakens the consensus mechanism's safety guarantees and can undermine the blockchain's finality, potentially allowing invalid blocks to be accepted.
Mitigation Recommendations
Upgrade Klever-Go to version 1.7.20 or later, where the issue is fixed. Patch status is confirmed by the vendor advisory indicating the fix in 1.7.20. No other mitigation is indicated.
CVE-2026-58262: CWE-345: Insufficient Verification of Data Authenticity in klever-io klever-go
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.
CVSS v4.0
Score 7.1high
Affected software
klever-io
klever-go
pkg:golang/github.com/klever-io/klever-goRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Klever-Go, the Go implementation of the Klever blockchain protocol, improperly counts unused padding bits of the PubKeysBitmap as valid signatures toward the two-thirds validator quorum in versions before 1.7.20. These padding bits do not correspond to any validator and are ignored by the actual BLS aggregate-signature check. A malicious or compromised block producer can exploit this by setting padding bits to falsely reach quorum, causing nodes to accept headers without a real two-thirds quorum. This undermines consensus safety and finality. The vulnerability is addressed in version 1.7.20.
Potential Impact
The vulnerability allows a block producer to bypass the required two-thirds validator signature quorum by exploiting unused padding bits, leading to acceptance of improperly signed headers. This weakens the consensus mechanism's safety guarantees and can undermine the blockchain's finality, potentially allowing invalid blocks to be accepted.
Mitigation Recommendations
Upgrade Klever-Go to version 1.7.20 or later, where the issue is fixed. Patch status is confirmed by the vendor advisory indicating the fix in 1.7.20. No other mitigation is indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-29T21:54:30.331Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a765831bf8831d5393f0c75
Added to database: 08/07/2026, 22:12:01 UTC
Last enriched: 08/15/2026, 14:42:58 UTC
Last updated: 09/22/2026, 01:52:44 UTC
Views: 60
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.