CVE-2026-49343: Klever-Go is the Go implementation of the Klever blockchain protocol

Q: How do I fix CVE-2026-49343?

No fixed release is listed yet. Watch the vendor advisory and apply any mitigation shown on this page.

Q: Is CVE-2026-49343 being exploited?

CVE-2026-49343 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-49343 affect?

CVE-2026-49343 affects affected software. Severity is medium (CVSS 5.9). 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

Q: How urgent is CVE-2026-49343?

Priority 37/100. CISA SSVC: public proof of concept; Remotely exploitable, no login, no user action

Routine

MEDIUM 5.9REMOTE

CVE-2026-49343 is a medium-severity flaw (CVSS 5.9) affecting affected software. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 t

Why this priority

CISA SSVC: public proof of concept
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 66%)
CISA exploited list	No
Weakness	CWE-400, CWE-772
Published	2026-08-07
Last modified	2026-10-24

Publisher (CNA): GitHub, Inc.

Last updated 2026-10-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Timeline

2026-08-07 23:17 UTCPublished CVE record published
2026-10-24 16:10 UTCUpdated Record last modified

Exact fixes by distribution

Go · github.com/klever-io/klever-go · FIXED · 1.7.18 · vulnerable: < 1.7.18 · source

go get github.com/klever-io/klever-go@v1.7.18 go list -m github.com/klever-io/klever-go

Fedora 46 · clementine · FIXED · 1.4.2-1.fc46 · FEDORA-2026-3e748ef4d3 · source

sudo dnf upgrade --advisory=FEDORA-2026-3e748ef4d3

Public exploits and detection

Public code exists for this CVE. Treat unpatched systems as at risk, and only run PoCs in a lab.

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

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-49343?

No fixed release is listed yet. Watch the vendor advisory and apply any mitigation shown on this page.

Is CVE-2026-49343 being exploited?

CVE-2026-49343 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-49343 affect?

CVE-2026-49343 affects affected software. Severity is medium (CVSS 5.9). 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

How urgent is CVE-2026-49343?

Priority 37/100. CISA SSVC: public proof of concept; Remotely exploitable, no login, no user action

References

← Back to latest CVEs