CVE-2026-49343
- Source
- https://cve.org/CVERecord?id=CVE-2026-49343
- Import Source
- https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-49343.json
- JSON Data
- https://api.osv.dev/v1/vulns/CVE-2026-49343
- Aliases
- Downstream
- Related
- Published
- 2026-08-07T22:18:18.735Z
- Modified
- 2026-08-08T11:46:25.703698416Z
- Severity
-
- 5.9 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
- Summary
- Klever-Go KVM: Throttler slot leak in trie account-data sync causes epoch bootstrap / state sync DoS
- Details
-
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.
- Database specific
{ "cna_assigner": "GitHub_M", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/49xxx/CVE-2026-49343.json", "cwe_ids": [ "CWE-400", "CWE-772" ] }- References