CVE-2026-52880: CWE-400: Uncontrolled Resource Consumption in klever-io klever-go
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.
AI Analysis
Technical Summary
Klever-Go, the Go implementation of the Klever blockchain protocol, versions 1.7.14 through 1.7.17 are vulnerable to a denial of service caused by uncontrolled resource consumption. The REST APIs use the Gin Engine.Run method which relies on Go's default HTTP server without configured ReadHeaderTimeout, ReadTimeout, or MaxHeaderBytes. This allows an unauthenticated remote attacker to open many connections that never complete their request headers, holding them open indefinitely and exhausting server file descriptors. This prevents the API from accepting legitimate connections. The vulnerability is resolved in version 1.7.18.
Potential Impact
An unauthenticated remote attacker can cause a denial of service by exhausting server file descriptors through slow-header HTTP connections, making the REST API unavailable to legitimate users. There is no impact on confidentiality or integrity reported.
Mitigation Recommendations
Upgrade Klever-Go to version 1.7.18 or later, where this issue is fixed. No other mitigation or temporary workaround is documented.
CVE-2026-52880: CWE-400: Uncontrolled Resource Consumption in klever-io klever-go
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.
CVSS v3.1
Score 7.5high
Affected software
pkg:golang/github.com/klever-io/klever-goRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Klever-Go, the Go implementation of the Klever blockchain protocol, versions 1.7.14 through 1.7.17 are vulnerable to a denial of service caused by uncontrolled resource consumption. The REST APIs use the Gin Engine.Run method which relies on Go's default HTTP server without configured ReadHeaderTimeout, ReadTimeout, or MaxHeaderBytes. This allows an unauthenticated remote attacker to open many connections that never complete their request headers, holding them open indefinitely and exhausting server file descriptors. This prevents the API from accepting legitimate connections. The vulnerability is resolved in version 1.7.18.
Potential Impact
An unauthenticated remote attacker can cause a denial of service by exhausting server file descriptors through slow-header HTTP connections, making the REST API unavailable to legitimate users. There is no impact on confidentiality or integrity reported.
Mitigation Recommendations
Upgrade Klever-Go to version 1.7.18 or later, where this issue is fixed. No other mitigation or temporary workaround is documented.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-08T21:44:27.364Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a7662babf8831d5394db833
Added to database: 08/07/2026, 22:56:58 UTC
Last enriched: 08/15/2026, 15:10:34 UTC
Last updated: 09/07/2026, 22:52:13 UTC
Views: 54
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.