CVE-2026-82407

HIGHPre-NVD 7.07.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 65% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
7.0
EG Score
7.0(medium)
EG Risk
48(Track)
EG Risk 48/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity70% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
35%
KEV
Not listed

Published

September 23, 2026

Last Modified

September 23, 2026

Advisory Details (4)

Auto-updated Sep 23, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

v1.7.20 - CertiK Audit Remediation & Coordinated Security Release

Patch available: klever-io/klever-go v1.7.20

https://github.com/klever-io/klever-go/releases/tag/v1.7.20
github_commit Patch Available

commit 642da9678938 (klever-io/klever-go)

Patch available: klever-io/klever-go v1.7.20 (contains commit 642da9678938)

https://github.com/klever-io/klever-go/commit/642da967893884d635986fed3c43bdc679cbfe8f
github_commit Patch Available

commit 11606a90ccc2 (klever-io/klever-go)

Patch available: klever-io/klever-go v1.7.20 (contains commit 11606a90ccc2)

https://github.com/klever-io/klever-go/commit/11606a90ccc289f93d0175994733229b332d9cff
github Patch Available🟡 PoC Available

Validator registration accepts an unvalidated BLS public key → consensus liveness DoS · Advisory · klever-io/klever-go · GitHub

https://github.com/klever-io/klever-go/security/advisories/GHSA-9wh6-9hq7-9688

Vendor Advisories for CVE-2026-82407(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 22:57 UTCEG score recompute
  2. 2026-09-24 14:04 UTCEPSS rescore
  3. 2026-09-24 09:30 UTCEG score recompute
  4. 2026-09-23 20:22 UTCEG score recompute
  5. 2026-09-23 19:48 UTCEG score recompute
  6. 2026-09-23 19:19 UTCEG score recompute
  7. 2026-09-23 19:19 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82407?
CVE-2026-82407 is a high vulnerability published on September 23, 2026. 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…
When was CVE-2026-82407 disclosed?
CVE-2026-82407 was first published in the National Vulnerability Database on September 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82407 actively exploited?
CVE-2026-82407 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 65.1% of all scored CVEs.
What is the CVSS score of CVE-2026-82407?
CVE-2026-82407 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-82407?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82407, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-82407

Explore →

Is Your Infrastructure Affected by CVE-2026-82407?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs