CVE-2026-58262

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 98% 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
7.1EG
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.1Exploit: None knownExposed: 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, header signature verification counts the unused padding bits of the PubKeysBitmap toward the two-thirds validator quorum. These padding bits do not correspond to any validator and are ignored by the actual BLS aggregate-signature check, so a malicious or compromised block producer can set them to reach the required quorum while gathering fewer genuine validator signatures than the protocol demands. As a result, nodes that import or intercept the header accept it as correctly signed without a real two-thirds quorum, weakening consensus safety and undermining finality. This issue is fixed in version 1.7.20.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

August 7, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Aug 7, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit.
github_commit Patch Available

commit a11cb28e495e (klever-io/klever-go)

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

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

Block aggregate-signature quorum can be satisfied with fewer than the required BLS signatures by setting unused (padding) bits in PubKeysBitmap · Advisory · klever-io/klever-go · GitHub

https://github.com/klever-io/klever-go/security/advisories/GHSA-f9h7-4mmq-vgcq

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 48× 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-19 20:10 UTCEG score recompute
  2. 2026-09-19 06:40 UTCEG score recompute
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 03:28 UTCEG score recompute
  5. 2026-09-17 19:31 UTCEPSS rescore
  6. 2026-09-17 00:53 UTCEG score recompute
  7. 2026-09-16 14:08 UTCEPSS rescore
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 04:34 UTCEG score recompute
  10. 2026-09-15 03:11 UTCEPSS rescore
  11. 2026-09-14 03:58 UTCEG score recompute
  12. 2026-09-13 16:47 UTCEPSS rescore
  13. 2026-09-13 03:17 UTCEG score recompute
  14. 2026-09-12 02:41 UTCEG score recompute
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-11 14:21 UTCEG score recompute
  17. 2026-09-10 12:40 UTCEG score recompute
  18. 2026-09-10 09:35 UTCEPSS rescore
  19. 2026-09-09 05:59 UTCEG score recompute
  20. 2026-09-08 22:01 UTCEPSS rescore
  21. 2026-09-06 16:45 UTCEG score recompute
  22. 2026-09-06 13:47 UTCEPSS rescore
  23. 2026-09-05 02:20 UTCEG score recompute
  24. 2026-09-04 08:50 UTCEG score recompute
  25. 2026-09-04 05:07 UTCEPSS rescore
Show 48 more
  1. 2026-09-03 03:59 UTCEG score recompute
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 17:37 UTCEG score recompute
  4. 2026-09-01 13:54 UTCEPSS rescore
  5. 2026-09-01 04:40 UTCEPSS rescore
  6. 2026-08-30 23:14 UTCEG score recompute
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 10:56 UTCEG score recompute
  9. 2026-08-30 01:22 UTCEPSS rescore
  10. 2026-08-29 10:20 UTCEG score recompute
  11. 2026-08-28 21:42 UTCEPSS rescore
  12. 2026-08-27 21:32 UTCEG score recompute
  13. 2026-08-27 14:25 UTCEPSS rescore
  14. 2026-08-26 20:56 UTCEG score recompute
  15. 2026-08-26 14:46 UTCEPSS rescore
  16. 2026-08-25 19:55 UTCEG score recompute
  17. 2026-08-25 13:49 UTCEPSS rescore
  18. 2026-08-24 19:19 UTCEG score recompute
  19. 2026-08-23 06:25 UTCEG score recompute
  20. 2026-08-23 00:19 UTCEPSS rescore
  21. 2026-08-22 05:49 UTCEG score recompute
  22. 2026-08-21 23:49 UTCEPSS rescore
  23. 2026-08-21 05:13 UTCEG score recompute
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 04:37 UTCEG score recompute
  26. 2026-08-19 17:04 UTCEPSS rescore
  27. 2026-08-18 15:39 UTCEG score recompute
  28. 2026-08-18 13:48 UTCEPSS rescore
  29. 2026-08-17 14:02 UTCEG score recompute
  30. 2026-08-17 13:47 UTCEPSS rescore
  31. 2026-08-17 01:45 UTCEG score recompute
  32. 2026-08-16 14:56 UTCEPSS rescore
  33. 2026-08-16 13:27 UTCEG score recompute
  34. 2026-08-16 02:14 UTCEPSS rescore
  35. 2026-08-15 12:51 UTCEG score recompute
  36. 2026-08-15 01:30 UTCEPSS rescore
  37. 2026-08-13 23:57 UTCEG score recompute
  38. 2026-08-13 22:00 UTCEPSS rescore
  39. 2026-08-12 23:22 UTCEG score recompute
  40. 2026-08-12 22:21 UTCEG score recompute
  41. 2026-08-12 13:51 UTCEPSS rescore
  42. 2026-08-11 00:23 UTCEG score recompute
  43. 2026-08-11 00:00 UTCEPSS rescore
  44. 2026-08-08 23:09 UTCEG score recompute
  45. 2026-08-08 16:37 UTCEPSS rescore
  46. 2026-08-07 22:33 UTCEG score recompute
  47. 2026-08-07 22:12 UTCEG score recompute
  48. 2026-08-07 22:12 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58262?
CVE-2026-58262 is a high vulnerability published on August 7, 2026. Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, header signature verification counts the unused padding bits of the PubKeysBitmap toward the two-thirds validator quorum. These padding bits do not correspond to any validator and are ignored by the actual BLS…
When was CVE-2026-58262 disclosed?
CVE-2026-58262 was first published in the National Vulnerability Database on August 7, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58262 actively exploited?
CVE-2026-58262 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 98.1% of all scored CVEs.
What is the CVSS score of CVE-2026-58262?
CVE-2026-58262 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-58262?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58262, 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-58262

Explore →

Is Your Infrastructure Affected by CVE-2026-58262?

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

Start Free Scan →Browse All CVEs