{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-52879", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2026-06-08T21:44:27.364Z", "datePublished": "2026-08-07T22:36:53.980Z", "dateUpdated": "2026-08-07T22:36:53.980Z"}, "containers": {"cna": {"title": "Klever-Go: Unbounded goroutine spawn on direct-message ingress enables peer-driven DoS", "problemTypes": [{"descriptions": [{"cweId": "CWE-400", "lang": "en", "description": "CWE-400: Uncontrolled Resource Consumption", "type": "CWE"}]}, {"descriptions": [{"cweId": "CWE-770", "lang": "en", "description": "CWE-770: Allocation of Resources Without Limits or Throttling", "type": "CWE"}]}], "metrics": [{"cvssV3_1": {"attackComplexity": "LOW", "attackVector": "NETWORK", "availabilityImpact": "HIGH", "baseScore": 7.5, "baseSeverity": "HIGH", "confidentialityImpact": "NONE", "integrityImpact": "NONE", "privilegesRequired": "NONE", "scope": "UNCHANGED", "userInteraction": "NONE", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "version": "3.1"}}], "references": [{"name": "https://github.com/klever-io/klever-go/security/advisories/GHSA-hf2g-6j7h-98wg", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/klever-io/klever-go/security/advisories/GHSA-hf2g-6j7h-98wg"}, {"name": "https://github.com/klever-io/klever-go/releases/tag/v1.7.18", "tags": ["x_refsource_MISC"], "url": "https://github.com/klever-io/klever-go/releases/tag/v1.7.18"}], "affected": [{"vendor": "klever-io", "product": "klever-go", "versions": [{"version": ">= 1.7.14, < 1.7.18", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2026-08-07T22:36:53.980Z"}, "descriptions": [{"lang": "en", "value": "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 connected peer can open a direct-send stream and send a stream of well-formed messages to force unbounded goroutine creation, where each goroutine allocates its own stack and holds a message reference until processing completes, adding scheduler and garbage-collection pressure faster than the runtime can drain it. This lets one peer degrade the node's availability and its ability to process legitimate traffic, resulting in a remotely triggerable denial of service. The issue is fixed in 1.7.18."}], "source": {"advisory": "GHSA-hf2g-6j7h-98wg", "discovery": "UNKNOWN"}}}}

{}

{}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[1.7.14,1.7.18)"}}], "enrichment": {"confidence": 100.0, "confidence_source": "matching", "scores": [{"score": 100.0, "source": "matching"}]}, "original": {"product": "klever-go", "source": "cna", "vendor": "klever-io"}, "product": "klever-go", "vendor": "klever-io"}], "created": "2026-08-07T23:30:17.446298+00:00", "updated": "2026-08-07T23:30:17.649549+00:00", "vendors": ["klever-io", "klever-io$PRODUCT$klever-go"]}