Vulnerability · Published Sep 23, 2026 · Assigned by GitHub_M

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

High 7.0

In plain English

A high-severity improper input validation in klever-go from klever-io. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.5% (higher than 41% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 4.0)7.0High
Exploit odds (30 days)0.5%top 59.5% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack toolingNoneno public tooling known

Official description

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 packages & fixed versions

EcosystemPackageFixed inAdvisory
Gogithub.com/klever-io/klever-go1.7.20GHSA-9wh6-9hq7-9688
Gogithub.com/klever-io/klever-go1.7.20GO-2026-6586

Affected products (as reported)

VendorProductVersions
klever-io klever-go < 1.7.20

Weakness: CWE-20 · Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H

References