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 82% 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%CVSS: 5.9Exploit: 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. 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.9(medium)
EG Risk
43(Track)
EG Risk 43/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
Severity59% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

June 5, 2026

Last Modified

August 13, 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

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 rangeFixed inDependents
github.com/klever-io/klever-go—1.7.18—

Weakness Classification(2)

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

Data Freshness Timeline

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

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 in the National Vulnerability Database on June 5, 2026, with the most recent update on August 13, 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% probability of exploitation in the next 30 days, which ranks it in the top 81.5% of all scored CVEs.
What is the CVSS score of CVE-2026-49343?
CVE-2026-49343 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-49343?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49343, 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-49343

Explore →

Is Your Infrastructure Affected by CVE-2026-49343?

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

Start Free Scan →Browse All CVEs