CVE-2026-82407: Klever-Go Denial of Service Vulnerability

HIGH
Advisory Identifier: GHSA-9wh6-9hq7-9688
CWE-20
Published
Advisory Summary

CVE-2026-82407 is a HIGH denial of service vulnerability (CWE-20: Improper Input Validation) affecting Klever-Go libraries in the Go ecosystem. The issue involves validator registration accepts an unvalidated bls public key → consensus liveness dos. Remediation is available by upgrading affected packages to version 1.7.20.

CVE-2026-82407 at a Glance

CVE Identifier CVE-2026-82407
GHSA Identifier GHSA-9wh6-9hq7-9688
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-20: Improper Input Validation
Affected Product Klever-Go
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-82407

To remediate this vulnerability, upgrade all affected Klever-Go dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/klever-io/klever-go fixed: 1.7.20
Upgrade github.com/klever-io/klever-go to 1.7.20
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/klever-io/klever-go

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-82407, inspect your project dependencies for Klever-Go:

inspect dependencies for github.com/klever-io/klever-go

Analyze the terminal output to locate any version of Klever-Go in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.7.20), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-20: Improper Input Validation, where the product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. In Klever-Go, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

**Location:** `core/kapp/validators/validators.go:201` (`Register`), (`genesis/checking/nodesSetupChecker.go:73`). `core/consensus/slot/bls/subslotStartSlot.go:165` `core/consensus/.../headerSignatureVerify.go:123` (`Create(...)`). ### Description Klever uses a BDN (Boneh-Drijvers-Neven) BLS multi-signature over BLS12-381 to finalize blocks (`crypto/signing/mcl/multisig/bls.go`, herumi/bls-go-binary). The library is initialized with only `bls.Init(bls.BLS12_381)` and no order-verification flags, so `Deserialize` does not enforce prime-order-subgroup membership subgroup safety relies on explicit `IsValidOrder()` calls in the wrappers. Runtime validator registration (`validators.Register`) stores the submitted 96-byte `BLSPublicKey` via `SetBLSPublicKey` with **no curve check, no subgroup check, and no proof-of-possession** (`CreateValidatorContract` carries the key but no signature proving key ownership; grep confirms no `proofOfPossession`/`VerifyProof`/`BLSSignature` verification anywhere in `core/kapp/validators/`). `CheckPublicKeyValid` — which does `IsValid && IsValidOrder && !IsZero` — runs only at genesis, not on runtime registration/update. ### POC Attack: (1) stake the minimum to register a validator, submitting a 96-byte `BLSPublicKey` that is not a valid G2 point (arbitrary bytes). Registration succeeds. (2) Once the validator is eligible and selected into a consensus group, every in-group node including the honest leader (`group[0]`) calls `MultiSigner().Reset(groupPubKeys, selfIndex)` at slot start, which deserializes all group keys via `PublicKeyFromByteArray` → herumi `Deserialize` **deterministically fails** on the malformed key → `SetSlotCanceled(true)`. The verify side (`Create(consensusPubKeys)`) fails identically. No block is produced for that round. ### Impact Every consensus round whose group contains the malformed-key validator is a missed slot. One eligible bad-key validator poisons roughly a `groupSize / eligibleSet` fraction of rounds → sustained liveness degradation. **Where the consensus group equals the eligible set (small or early-stage networks), this is a full chain halt.** Cost is the minimum validator stake, permissionless, and repeatable; no fork flag gates the missing validation. Rated **High** (Byzantine liveness; Critical on small validator sets). The severity scales down to a fractional missed-slot / throughput-degradation attack on a large validator set where the bad validator is only occasionally in the active group. ### Recommendation Enforce `CheckPublicKeyValid` (curve + prime-order subgroup + non-zero) on the submitted BLS key at runtime validator registration and config-update, and ideally require a proof-of-possession (a BLS signature over the validator's own key/identity) at registration to prove key ownership and well-formedness. Gate the stricter validation behind an epoch fork flag for reprocessing consistency.

CVE-2026-82407 Affected Klever-Go Versions

1 component(s)
Fixed Versions:
1.7.20
Product / Package Ecosystem Affected Versions Fixed Version
github.com/klever-io/klever-go
Go
< 1.7.20
1.7.20

References

Frequently Asked Questions

What is CVE-2026-82407?
CVE-2026-82407 is a security vulnerability in Klever-Go involving Validator registration accepts an unvalidated BLS public key → consensus liveness DoS under CWE-20: Improper Input Validation.
Which Klever-Go versions are affected?
Affected versions include releases prior to 1.7.20 across affected packages: github.com/klever-io/klever-go.
What version fixes CVE-2026-82407?
Upgrading to 1.7.20 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/klever-io/klever-go affected?
Yes, github.com/klever-io/klever-go is affected in releases prior to 1.7.20. Upgrade your dependency to 1.7.20 or later.
What CWE is associated with CVE-2026-82407?
CVE-2026-82407 is classified under CWE-20: Improper Input Validation (The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.).
How can I check Go dependencies for CVE-2026-82407?
Run the dependency tree command: 'inspect dependencies for github.com/klever-io/klever-go'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-9wh6-9hq7-9688",
  "modified" : "2026-09-23T21:24:08Z",
  "published" : "2026-09-23T21:24:08Z",
  "aliases" : [ "CVE-2026-82407" ],
  "summary" : "Klever-Go: Validator registration accepts an unvalidated BLS public key → consensus liveness DoS",
  "details" : "**Location:** `core/kapp/validators/validators.go:201` (`Register`), (`genesis/checking/nodesSetupChecker.go:73`). `core/consensus/slot/bls/subslotStartSlot.go:165` `core/consensus/.../headerSignatureVerify.go:123` (`Create(...)`).\n\n### Description\n\nKlever uses a BDN (Boneh-Drijvers-Neven) BLS multi-signature over BLS12-381 to finalize blocks (`crypto/signing/mcl/multisig/bls.go`, herumi/bls-go-binary). The library is initialized with only `bls.Init(bls.BLS12_381)` and no order-verification flags, so `Deserialize` does not enforce prime-order-subgroup membership  subgroup safety relies on explicit `IsValidOrder()` calls in the wrappers.\n\nRuntime validator registration (`validators.Register`) stores the submitted 96-byte `BLSPublicKey` via `SetBLSPublicKey` with **no curve check, no subgroup check, and no proof-of-possession** (`CreateValidatorContract` carries the key but no signature proving key ownership; grep confirms no `proofOfPossession`/`VerifyProof`/`BLSSignature` verification anywhere in `core/kapp/validators/`). `CheckPublicKeyValid` — which does `IsValid && IsValidOrder && !IsZero` — runs only at genesis, not on runtime registration/update.\n\n### POC\n\nAttack: \n(1) stake the minimum to register a validator, submitting a 96-byte `BLSPublicKey` that is not a valid G2 point (arbitrary bytes). Registration succeeds. \n(2) Once the validator is eligible and selected into a consensus group, every in-group node  including the honest leader (`group[0]`)  calls `MultiSigner().Reset(groupPubKeys, selfIndex)` at slot start, which deserializes all group keys via `PublicKeyFromByteArray` → herumi `Deserialize` **deterministically fails** on the malformed key → `SetSlotCanceled(true)`. The verify side (`Create(consensusPubKeys)`) fails identically. No block is produced for that round. \n\n\n\n### Impact\n\nEvery consensus round whose group contains the malformed-key validator is a missed slot. One eligible bad-key validator poisons roughly a `groupSize / eligibleSet` fraction of rounds → sustained liveness degradation. **Where the consensus group equals the eligible set (small or early-stage networks), this is a full chain halt.** Cost is the minimum validator stake, permissionless, and repeatable; no fork flag gates the missing validation. \n\nRated **High** (Byzantine liveness; Critical on small validator sets). The severity scales down to a fractional missed-slot / throughput-degradation attack on a large validator set where the bad validator is only occasionally in the active group.\n\n### Recommendation\n\nEnforce `CheckPublicKeyValid` (curve + prime-order subgroup + non-zero) on the submitted BLS key at runtime validator registration and config-update, and ideally require a proof-of-possession (a BLS signature over the validator's own key/identity) at registration to prove key ownership and well-formedness. Gate the stricter validation behind an epoch fork flag for reprocessing consistency.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/klever-io/klever-go"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.7.20"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.7.19"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/klever-io/klever-go/security/advisories/GHSA-9wh6-9hq7-9688"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/klever-io/klever-go/commit/11606a90ccc289f93d0175994733229b332d9cff"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/klever-io/klever-go/commit/642da967893884d635986fed3c43bdc679cbfe8f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/klever-io/klever-go"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/klever-io/klever-go/releases/tag/v1.7.20"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-20" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-23T21:24:08Z",
    "nvd_published_at" : null
  }
}