{"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-82406 exists.","fix":"Upgrade github.com/klever-io/klever-go to 1.7.20 or later.","what":"CVE-2026-82406 is a high-severity vulnerability in klever-io klever-go, published on 23 Sep 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-82406 and fix it if it is affected.\n\nWhat it is: CVE-2026-82406 is a high-severity vulnerability in klever-io klever-go, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-82406 exists.\n\nAffected packages and fixed versions:\n- github.com/klever-io/klever-go (Go): affected all versions; fixed in 1.7.20\n- github.com/klever-io/klever-go (Go): affected all versions; fixed in 1.7.20\n- github.com/klever-io/klever-go (Go): affected all versions; fixed in 1.7.20\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-82406/ (Markdown: https://insights.sbomify.com/CVE-2026-82406/index.md)","id":"CVE-2026-82406","markdown":"https://insights.sbomify.com/CVE-2026-82406/index.md","name":"CVE-2026-82406","record":{"aliases":["GHSA-26r5-4mm2-px5c","GO-2026-6584"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","other"],"network_reachable":"yes","non_default_config":false,"product_category":"Klever blockchain protocol","requires_auth":"low_privilege","summary":"Attackers can exploit missing state checks in the marketplace to steal funds or NFTs by bypassing claimed order restrictions.","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-841","name":"Improper Enforcement of Behavioral Workflow"}],"description":"Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, the native marketplace function core/kapp/market/market.go Buy does not check IsClaimed before accepting a bid. A seller can use the Claim seller-accept branch to settle a resting-bid auction while leaving the claimed order loadable with a future EndTime and stale CurrentBid and CurrentBidder values. A later bidder can submit a higher bid, be debited, and cause the previous bidder to receive a refund even though the NFT has already been delivered. Because Claim and CancelOrder reject the later bidder when IsClaimed is true, the later bidder cannot obtain the NFT or recover the funds. This issue is fixed in version 1.7.20.","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: Zombie-order theft: `Buy` missing `IsClaimed` guard in native marketplace","id":"CVE-2026-82406","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Klever-Go: Validator registration accepts an unvalidated BLS public key → consensus liveness DoS","id":"CVE-2026-82407"},"packages":[{"ecosystem":"Go","fixed":["1.7.20"],"introduced":["0"],"last_affected":[],"package":"github.com/klever-io/klever-go","purl":null,"source":"GHSA-26r5-4mm2-px5c"},{"ecosystem":"Go","fixed":["1.7.20"],"introduced":["0"],"last_affected":[],"package":"github.com/klever-io/klever-go","purl":"pkg:golang/github.com/klever-io/klever-go","source":"GHSA-26r5-4mm2-px5c"},{"ecosystem":"Go","fixed":["1.7.20"],"introduced":["0"],"last_affected":[],"package":"github.com/klever-io/klever-go","purl":"pkg:golang/github.com/klever-io/klever-go","source":"GO-2026-6584"}],"prev":{"headline":"Klever-Go Account takeover: `kleverUpdateAccountPermission` authorizes on attacker-controlled `RecipientAddr` instead of the authenticated caller","id":"CVE-2026-82405"},"products":["klever-go"],"published":"2026-09-23","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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-24","vendors":["klever-io"]},"summary":"Attackers can exploit missing state checks in the marketplace to steal funds or NFTs by bypassing claimed order restrictions.","url":"https://insights.sbomify.com/CVE-2026-82406/"}