CVE-2026-52879

{"id": "CVE-2026-52879", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-52879", "role": "CISA Coordinator", "options": [{"exploitation": "poc"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-10T13:35:42.857307Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.5, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "NONE", "confidentialityImpact": "NONE"}, "impactScore": 3.6, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "klever-io", "product": "klever-go", "versions": [{"status": "affected", "version": ">= 1.7.14, < 1.7.18"}]}]}], "published": "2026-08-07T23:17:04.743", "references": [{"url": "https://github.com/klever-io/klever-go/releases/tag/v1.7.18", "source": "security-advisories@github.com"}, {"url": "https://github.com/klever-io/klever-go/security/advisories/GHSA-hf2g-6j7h-98wg", "source": "security-advisories@github.com"}, {"url": "https://github.com/klever-io/klever-go/security/advisories/GHSA-hf2g-6j7h-98wg", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-400"}, {"lang": "en", "value": "CWE-770"}]}], "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."}, {"lang": "es", "value": "Klever-Go es la implementaci\u00f3n en Go del protocolo blockchain de Klever. En las versiones 1.7.14 a la 1.7.17, el gestor de entrada de mensajes directos crea una nueva goroutine para cada mensaje directo entrante antes de que la capa antiflood a nivel de procesador tome cualquier decisi\u00f3n de admisi\u00f3n, sin sem\u00e1foro, limitador o l\u00edmite en el n\u00famero de creaciones concurrentes en curso. Debido a que la verificaci\u00f3n antiflood se ejecuta dentro de la goroutine creada en lugar de antes de ella, un \u00fanico par conectado puede abrir un flujo de env\u00edo directo y enviar un flujo de mensajes bien formados para forzar la creaci\u00f3n ilimitada de goroutines, donde cada goroutine asigna su propia pila y mantiene una referencia al mensaje hasta que el procesamiento se completa, a\u00f1adiendo presi\u00f3n al planificador y a la recolecci\u00f3n de basura m\u00e1s r\u00e1pido de lo que el tiempo de ejecuci\u00f3n puede drenarla. Esto permite que un par degrade la disponibilidad del nodo y su capacidad para procesar tr\u00e1fico leg\u00edtimo, resultando en una denegaci\u00f3n de servicio que puede ser activada remotamente. El problema est\u00e1 solucionado en la 1.7.18."}], "lastModified": "2026-10-24T16:10:00.153", "sourceIdentifier": "security-advisories@github.com"}