Vulnerability 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.
Related Weaknesses (CWE)
References
- https://github.com/klever-io/klever-go/commit/a11cb28e495e608d8034dbe83a91e89d0c
- https://github.com/klever-io/klever-go/security/advisories/GHSA-f9h7-4mmq-vgcq
FAQ
What is CVE-2026-58262?
CVE-2026-58262 is a documented vulnerability. 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...
How severe is CVE-2026-58262?
CVSS scoring is not yet available for CVE-2026-58262. Check NVD for updates.
Is there a patch for CVE-2026-58262?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.