{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-58262 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-58262 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-58262 is a high-severity vulnerability in klever-io klever-go, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-58262 and fix it if it is affected.\n\nWhat it is: CVE-2026-58262 is a high-severity vulnerability in klever-io klever-go, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-58262 in the wild and no public exploit code.\n\nAffected product: klever-io klever-go. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-58262/ (Markdown: https://insights.sbomify.com/CVE-2026-58262/index.md)","id":"CVE-2026-58262","markdown":"https://insights.sbomify.com/CVE-2026-58262/index.md","name":"CVE-2026-58262","record":{"aliases":["GHSA-f9h7-4mmq-vgcq"],"analysis":{"component_type":"other","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Klever blockchain protocol","requires_auth":"low_privilege","summary":"A malicious block producer can bypass BLS signature quorum checks by exploiting padding bits, compromising consensus safety in Klever-Go nodes.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, header signature verification counts the unused padding bits of the PubKeysBitmap toward the two-thirds validator quorum. These padding bits do not correspond to any validator and are ignored by the actual BLS aggregate-signature check, so a malicious or compromised block producer can set them to reach the required quorum while gathering fewer genuine validator signatures than the protocol demands. As a result, nodes that import or intercept the header accept it as correctly signed without a real two-thirds quorum, weakening consensus safety and undermining finality. This issue is fixed in version 1.7.20.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Klever-Go: PubKeysBitmap padding bits bypass the BLS signature quorum","id":"CVE-2026-58262","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Jodit Editor: Mutation XSS in jodit clean-html via a MathML/style rawtext carrier","id":"CVE-2026-58263"},"packages":[],"prev":{"headline":"GRR vulnerable to Arbitrary File Read and Deletion","id":"CVE-2026-58257"},"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-12","vendors":["klever-io"]},"summary":"A malicious block producer can bypass BLS signature quorum checks by exploiting padding bits, compromising consensus safety in Klever-Go nodes.","url":"https://insights.sbomify.com/CVE-2026-58262/"}