CVE-2026-52878

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% 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
Elevated
7.5EG
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.5Exploit: 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. Versions 1.7.14 through 1.7.17 are vulnerable to a nil-pointer panic triggered by a protobuf Transaction whose embedded RawData sub-message is omitted. This omission causes RawData to decode to nil. Every transaction gossiped on the Klever-Go P2P network is decoded and validated synchronously inside the libp2p pubsub topic-validator callback, where txVersionChecker.CheckTxVersion dereferences tx.RawData.Version with no nil check. Because the libp2p pubsub callback, the underlying go-libp2p-pubsub validation worker, and Klever's own network/p2p layer install no recover(), the panic propagates and crashes the entire node process. The attacker payload is a 3-byte protobuf message; no validator key, stake, funds, or on-chain account is required, and delivery aimed at enough of the BLS validator set can halt block production, resulting in a chain halt. This issue has been fixed in version 1.7.18.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
65(Attend)
EG Risk 65/100SSVC: Attend

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

June 5, 2026

Last Modified

August 10, 2026

Advisory Details (2)

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

v1.7.18 - Coordinated Security Release

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

https://github.com/klever-io/klever-go/releases/tag/v1.7.18
github Patch Available🟡 PoC Available

Unauthenticated remote node crash (nil-pointer DoS) in klever-go P2P transaction interceptor (txVersionChecker nil RawData) - potential chain halt · Advisory · klever-io/klever-go · GitHub

https://github.com/klever-io/klever-go/security/advisories/GHSA-rm5c-5x2p-48wr

Vendor Advisories for CVE-2026-52878(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/klever-io/klever-go—1.7.18—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-52878?
CVE-2026-52878 is a high vulnerability published on June 5, 2026. Klever-Go is the Go implementation of the Klever blockchain protocol. Versions 1.7.14 through 1.7.17 are vulnerable to a nil-pointer panic triggered by a protobuf Transaction whose embedded RawData sub-message is omitted. This omission causes RawData to decode to nil. Every transaction gossiped on…
When was CVE-2026-52878 disclosed?
CVE-2026-52878 was first published in the National Vulnerability Database on June 5, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52878 actively exploited?
CVE-2026-52878 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 79.5% of all scored CVEs.
What is the CVSS score of CVE-2026-52878?
CVE-2026-52878 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-52878?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52878, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-52878

Explore →

Is Your Infrastructure Affected by CVE-2026-52878?

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

Start Free Scan →Browse All CVEs