Live › vulnerability › CVE-2026-82406
Go to dashboardKlever-Go, the Go implementation of the Klever blockchain, lets a buyer place a bid on an already-claimed marketplace order, so a later bidder is debited and cannot get the NFT or a refund. The flaw is that the native marketplace Buy function skips the IsClaimed check, so an attacker-controlled seller or bidder can take funds from later bidders.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| github.com/klever-io/klever-go | go | < 1.7.20 | 1.7.20 |
1.7.201.7.20 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-82406")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.