CVE-2026-52880

Received Received - Intake

Denial of Service in Klever-Go Blockchain Protocol

Publication date: 2026-08-07

Last updated on: 2026-08-07

Assigner: GitHub, Inc.

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-07

Last Modified

2026-08-07

Generated

2026-08-08

AI Q&A

2026-08-08

EPSS Evaluated

N/A

NVD

CVE-2026-52880

Affected Vendors & Products

Vendor	Product	Version / Range
klever	klever-go	From 1.7.14 (inc) to 1.7.17 (inc)
klever	klever-go	1.7.18

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-400	The product does not properly control the allocation and maintenance of a limited resource.
CWE-770	The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.

Attack-Flow Graph

Executive Summary

Klever-Go versions 1.7.14 through 1.7.17 contain a remotely triggerable denial of service vulnerability. The REST APIs use Go's default HTTP server without timeouts or header limits. Attackers can exploit this by sending slow or incomplete request headers, holding connections open indefinitely until server resources are exhausted.

Detection Guidance

Check if Klever-Go versions 1.7.14 through 1.7.17 are running. Monitor for high file descriptor usage or slow/unresponsive REST API endpoints. Use netstat or ss to inspect open connections to the REST API ports.

Impact Analysis

If the REST API is exposed beyond localhost, a single unauthenticated attacker can consume all available file descriptors by opening many slow-header connections. This makes the API unavailable to legitimate users, effectively causing downtime for the service.

Compliance Impact

This vulnerability could impact compliance with GDPR and HIPAA by causing denial of service, potentially leading to unauthorized data access or processing disruptions. Unavailability of REST APIs may hinder required logging, monitoring, or audit functions.

Mitigation Strategies

Upgrade Klever-Go to version 1.7.18 or later. Restrict REST API access to localhost only. Configure timeouts and limits in the HTTP server settings. Monitor for suspicious connection patterns.

Hi! I’m here to help you understand CVE-2026-52880. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70