{"answers":{"affected":"3 open source packages ship an affected version, including github.com/klever-io/klever-go.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52878 exists.","fix":"Upgrade github.com/klever-io/klever-go to 1.7.18 or later.","what":"CVE-2026-52878 is a high-severity vulnerability in klever-io klever-go, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-52878 and fix it if it is affected.\n\nWhat it is: CVE-2026-52878 is a high-severity vulnerability in klever-io klever-go, published on 7 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-52878 exists.\n\nAffected packages and fixed versions:\n- github.com/klever-io/klever-go (Go): affected from 1.7.14; fixed in 1.7.18\n- github.com/klever-io/klever-go (Go): affected from 1.7.14; fixed in 1.7.18\n- github.com/klever-io/klever-go (Go): affected from 1.7.14; fixed in 1.7.18\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-52878/ (Markdown: https://insights.sbomify.com/CVE-2026-52878/index.md)","id":"CVE-2026-52878","markdown":"https://insights.sbomify.com/CVE-2026-52878/index.md","name":"CVE-2026-52878","record":{"aliases":["GHSA-rm5c-5x2p-48wr","GO-2026-5628"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Klever blockchain node","requires_auth":"none","summary":"An unauthenticated attacker can crash Klever-Go nodes and halt the blockchain by sending a malformed P2P transaction that triggers a nil-pointer panic.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"Klever-Go is the Go implementation of the Klever blockchain protocol. Versions 1.7.14 through 1.7.17 are vulnerable to a nil-pointer panic triggered by a protobuf Transaction whose embedded RawData sub-message is omitted. This omission causes RawData to decode to nil. Every transaction gossiped on the Klever-Go P2P network is decoded and validated synchronously inside the libp2p pubsub topic-validator callback, where txVersionChecker.CheckTxVersion dereferences tx.RawData.Version with no nil check. Because the libp2p pubsub callback, the underlying go-libp2p-pubsub validation worker, and Klever's own network/p2p layer install no recover(), the panic propagates and crashes the entire node process. The attacker payload is a 3-byte protobuf message; no validator key, stake, funds, or on-chain account is required, and delivery aimed at enough of the BLS validator set can halt block production, resulting in a chain halt. This issue has been fixed in version 1.7.18.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Klever-Go: Unauthenticated nil-pointer DoS in P2P transaction validation can halt the chain","id":"CVE-2026-52878","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"null_dereference","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"Klever-Go: Unbounded goroutine spawn on direct-message ingress enables peer-driven DoS","id":"CVE-2026-52879"},"packages":[{"ecosystem":"Go","fixed":["1.7.18"],"introduced":["1.7.14"],"last_affected":[],"package":"github.com/klever-io/klever-go","purl":null,"source":"GHSA-rm5c-5x2p-48wr"},{"ecosystem":"Go","fixed":["1.7.18"],"introduced":["1.7.14"],"last_affected":[],"package":"github.com/klever-io/klever-go","purl":"pkg:golang/github.com/klever-io/klever-go","source":"GHSA-rm5c-5x2p-48wr"},{"ecosystem":"Go","fixed":["1.7.18"],"introduced":["1.7.14"],"last_affected":[],"package":"github.com/klever-io/klever-go","purl":"pkg:golang/github.com/klever-io/klever-go","source":"GO-2026-5628"}],"prev":{"headline":"Streambert : Insecure Protocol Execution in open-external IPC Handler","id":"CVE-2026-52877"},"products":["klever-go"],"published":"2026-08-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-10","vendors":["klever-io"]},"summary":"An unauthenticated attacker can crash Klever-Go nodes and halt the blockchain by sending a malformed P2P transaction that triggers a nil-pointer panic.","url":"https://insights.sbomify.com/CVE-2026-52878/"}