Signal is active with 2 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
Klever-Go is the Go implementation of the Klever blockchain protocol. Versions from 1.7.14 through 1.7.17 are vulnerable to a remotely triggerable denial of service. Both REST APIs are started with the Gin Engine.Run convenience method, which serves requests through Go's default HTTP server with no ReadHeaderTimeout, ReadTimeout, or MaxHeaderBytes configured. As a result, incoming connections that never complete their request headers are held open indefinitely. When a REST listener is reachable beyond localhost through the documented all-interface bind or a Docker port-publish deployment, a single unauthenticated client can open many slow-header connections and hold them open until server file descriptors are exhausted, preventing the API from accepting new connections. This renders the REST API unavailable to legitimate clients. This issue is fixed in version 1.7.18.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
AVAILABLE
Momentum
NONE
CVE-2026-52880 Klever-Go is the Go implementation of the Klever blockchain protocol. Versions from 1.7.14 through 1.7.17 are vulnerable to a remotely triggerable denial of service. … https://www.cve.org/CVERecord?id=CVE-2026-52880
Post summary
CVE-2026-52880 is disclosed as a remotely triggerable denial‑of‑service vulnerability affecting Klever-Go versions 1.7.14 through 1.7.17, with no PoC, exploit, or patch information provided.
⛓️ Klever blockchain node DoS vulnerability disclosed CVE-2026-52880 — High severity Klever-Go 1.7.14–1.7.17 can be remotely overwhelmed through slow HTTP connections, exhausting file descriptors and making REST APIs unavailable. ✅ Fixed in 1.7.18. 🔎 Source: Tenable / GitHub Security Advisory. #Blockchain #Klever #DoS #CVE #CyberSecurity
Post summary
A high‑severity DoS vulnerability (CVE‑2026‑52880) in Klever‑Go was disclosed, with details on slow HTTP exploitation, and is already addressed in version 1.7.18.