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

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

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

Q: Is CVE-2026-52879 being exploited?

CVE-2026-52879 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-52879 affect?

CVE-2026-52879 affects affected software. Severity is high (CVSS 7.5). Klever-Go is the Go implementation of the Klever blockchain protocol. In versions 1.7.14 through 1.7.17, the direct-message ingress handler spawns a new goroutine for every incoming direct message before the processor-level antiflood layer

Q: How urgent is CVE-2026-52879?

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

This month

HIGH 7.5REMOTE

CVE-2026-52879 is a high-severity flaw (CVSS 7.5) 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 1.7.14 through 1.7.17, the direct-message ingress handler spawns a new goroutine for every incoming direct message before the processor-level antiflood layer makes any admission decision, with no semaphore, throttler, or bound on the number of concurrent in-flight spawns. Because the antiflood check runs inside the spawned goroutine rather than before it, a single c

Why this priority

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

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 59%)
CISA exploited list	No
Weakness	CWE-400, CWE-770
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.14, <= 1.7.17 · 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-hf2g-6j7h-98wg

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-52879?

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

Is CVE-2026-52879 being exploited?

CVE-2026-52879 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-52879 affect?

CVE-2026-52879 affects affected software. Severity is high (CVSS 7.5). Klever-Go is the Go implementation of the Klever blockchain protocol. In versions 1.7.14 through 1.7.17, the direct-message ingress handler spawns a new goroutine for every incoming direct message before the processor-level antiflood layer

How urgent is CVE-2026-52879?

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

References

← Back to latest CVEs