CVE-2026-58262
HIGH
7,1
Source: [email protected]
Attack Vector: network
Attack Complexity: low
Privileges Required: low
User Interaction: none
Confidentiality: N/A
Integrity: N/A
Availability: N/A
Description
AI Translation Available
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.
345
Insufficient Verification of Data Authenticity
DraftCommon Consequences
Security Scopes Affected:
Integrity
Other
Potential Impacts:
Varies By Context
Unexpected State
Applicable Platforms
Technologies:
ICS/OT
347
Improper Verification of Cryptographic Signature
DraftCommon Consequences
Security Scopes Affected:
Access Control
Integrity
Confidentiality
Potential Impacts:
Gain Privileges Or Assume Identity
Modify Application Data
Execute Unauthorized Code Or Commands
Applicable Platforms
All platforms may be affected
https://github.com/klever-io/klever-go/commit/a11cb28e495e608d8034dbe83a91e89d0…
https://github.com/klever-io/klever-go/security/advisories/GHSA-f9h7-4mmq-vgcq