Vulnerability · Published Aug 7, 2026 · Assigned by GitHub_M

CVE-2026-52880Klever-Go: REST API slow-header connection exhaustion via Gin Engine.Run

High 7.5

In plain English

A high-severity uncontrolled resource consumption in klever-go from klever-io. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.5% (higher than 42% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.5High
Exploit odds (30 days)0.5%top 57.8% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Gogithub.com/klever-io/klever-go1.7.18GO-2026-5686
Gogithub.com/klever-io/klever-go1.7.18GHSA-w4c6-7r69-w7j9

Affected products (as reported)

VendorProductVersions
klever-io klever-go >= 1.7.14, < 1.7.18

Weakness: CWE-400, CWE-770 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References