CVE-2026-58262: high-severity vulnerability in klever-io klever-go
Klever-Go: PubKeysBitmap padding bits bypass the BLS signature quorum
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.1epss 0.2%
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:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
Affected products
klever-io · klever-goRelated CVEs — klever-io klever-go
In the same product, most dangerous first.
CVE-2026-86064HIGHKlever-Go: /log controls global node loggingEPSS 0.6%CVE-2026-54755CRITICALKlever-Go: Integer overflow in split-royalty validation enables unbounded minting of KLV (native token)EPSS 0.6%CVE-2026-55764HIGHKlever-Go: SFT add-quantity `int64` overflow bypasses a finite per-nonce MaxSupplyEPSS 0.5%CVE-2026-55763HIGHKlever-Go: Percentage-transfer royalty skips the source debit at exactly-100% splitsEPSS 0.5%CVE-2026-52880HIGHKlever-Go: REST API slow-header connection exhaustion via Gin Engine.RunEPSS 0.5%CVE-2026-52879HIGHKlever-Go: Unbounded goroutine spawn on direct-message ingress enables peer-driven DoSEPSS 0.5%