Live › vulnerability › CVE-2026-82407
Go to dashboardKlever-Go, the Go implementation of the Klever blockchain node, accepts validator registrations with a BLS public key that is never checked for curve or subgroup validity. A malformed key lets anyone who registers a validator cause repeated missed consensus rounds, and in some configurations a full network halt.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| github.com/klever-io/klever-go | go | < 1.7.20 | 1.7.20 |
Run go list -m github.com/klever-io/klever-go in the node module and check whether the version is below 1.7.20.
Upgrade github.com/klever-io/klever-go to 1.7.20 or later.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, core/kapp/validators/validators.go Register and the runtime validator update path accept a submitted BLSPublicKey without curve, prime-order subgroup, or nonzero validation. When a validator with a malformed key becomes eligible and is selected into a consensus group, MultiSigner.Reset and the corresponding signature verification creation path cannot deserialize the group key and cancel the slot. This causes repeated missed rounds and throughput degradation, and a network whose consensus group equals the eligible validator set can halt completely. Genesis validation is not affected because that path already performs CheckPublicKeyValid. This issue is fixed in version 1.7.20.
This page as .md · .json · in your agent: get_signal("CVE-2026-82407")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.