CVE-2026-82407

published 23 Sep 2026 · updated 23 Sep 2026

Klever-Go: Validator registration accepts an unvalidated BLS public key → consensus liveness DoS

7.0HighCVSS 7.0EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. No fixed version is recorded.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
klever-io<1.7.20

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-82407 severity on Zeptric[![CVE-2026-82407](https://zeptric.io/badge/cve/CVE-2026-82407.svg)](https://zeptric.io/cve/CVE-2026-82407)