CVE-2026-58262
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
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 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.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| klever-io | klever-go | < 1.7.20 | affected |
Weaknesses
- CWE-345: CWE-345: Insufficient Verification of Data Authenticity
- CWE-347: CWE-347: Improper Verification of Cryptographic Signature
References
- https://github.com/klever-io/klever-go/security/advisories/GHSA-f9h7-4mmq-vgcq
- https://github.com/klever-io/klever-go/commit/a11cb28e495e608d8034dbe83a91e89d0c68e0f7
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.