CVE-2026-49343
MEDIUMDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 18% of all known CVEs.
References
Related Vulnerabilities
Other CWE-400 (Resource Exhaustion) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2023-44487 | High | 7.5 | 100% | KEV | Fix |
| CVE-2021-44228 | Critical | 10.0 | 100% | KEV + Ransom | Fix |
| CVE-2011-3192 | High | 7.8 | 99% | - | Fix |
| CVE-2019-11478 | Medium | 5.3 | 95% | - | Fix |
| CVE-2023-21547 | High | 7.5 | 89% | - | Fix |
| CVE-2024-25617 | Medium | 5.3 | 89% | - | Fix |
Common questions
How do I fix CVE-2026-49343?
No published fix for CVE-2026-49343 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-49343 being actively exploited?
Not that we know of. CVE-2026-49343 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.26% is the estimated probability that it will be exploited in the next 30 days. That is higher than 18% of all scored CVEs.
How severe is CVE-2026-49343?
CVE-2026-49343 has a CVSS v3 base score of 5.9, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-49343
Markdown
[](https://tridentstack.com/cve/CVE-2026-49343)HTML
<a href="https://tridentstack.com/cve/CVE-2026-49343"><img src="https://tridentstack.com/cve/badge/CVE-2026-49343.svg" alt="CVE-2026-49343"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-13.