CVE-2026-49343

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% 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
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.9Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Klever-Go is the Go implementation of the Klever blockchain protocol. In versions prior to 1.7.18, the account-data trie syncers are vulnerable to a resource-exhaustion flaw that leaks bounded throttler slots on error paths. In syncDataTrie() (in both userAccountsSyncer.go and kappAccountsSyncer.go), StartProcessing() reserves a slot from the NumGoRoutinesThrottler, but the corresponding EndProcessing() is only called on the success path and on the duplicate-root early return. As a result, any error from trie.NewTrie(), trie.NewTrieSyncer(), or trieSyncer.StartSyncing() (including the network-dependent timeout path) permanently consumes one slot for the lifetime of the throttler. An attacker who can repeatedly cause trie-node sync failures or timeouts during bootstrap can exhaust the bounded throttler, after which further account-data trie syncs stop making progress and SyncAccounts() returns a timeout. Because epoch bootstrap in syncUserAccountsState() and syncKappAccountsState() aborts on any such error, this causes bootstrap to fail, a core availability issue affecting fresh, restarting, or resyncing nodes and validators. This issue is fixed in version 1.7.18.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
43
EG Risk 43/100

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
Severity59% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

Published

June 5, 2026

Last Modified

September 9, 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
githubMentions a patch (unverified)🟡 PoC Available

Throttler slot leak in trie account-data sync causes epoch bootstrap / state sync DoS · Advisory · klever-io/klever-go · GitHub

https://github.com/klever-io/klever-go/security/advisories/GHSA-fw38-pc54-jvx9

Vendor Advisories for CVE-2026-49343(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 rangeFix by version rangeDependents
github.com/klever-io/klever-go—
  • every version up to 1.7.18: fixed in 1.7.18
—

Weakness Classification(2)

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

Data Freshness Timeline

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-49343?
CVE-2026-49343 is a medium vulnerability published on June 5, 2026. Klever-Go is the Go implementation of the Klever blockchain protocol. In versions prior to 1.7.18, the account-data trie syncers are vulnerable to a resource-exhaustion flaw that leaks bounded throttler slots on error paths. In syncDataTrie() (in both userAccountsSyncer.go and…
When was CVE-2026-49343 disclosed?
CVE-2026-49343 was first published on June 5, 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-49343 actively exploited?
CVE-2026-49343 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-49343?
CVE-2026-49343 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-49343?
A fix for CVE-2026-49343 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-49343 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-49343?

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

Book a Demo →Browse All CVEs