CVE-2026-82406
Severity not reportedKlever-Go is the Go implementation of the Klever blockchain protocol.
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.
Affected products
Not reported by the source (unknown — not "none").
Weakness classification (CWE)
Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://github.com/klever-io/klever-go/commit/063bb3ed98f9a84a4b1f7286680613a5fc3c91b2 security-advisories@github.com
- https://github.com/klever-io/klever-go/pull/16 security-advisories@github.com
- https://github.com/klever-io/klever-go/releases/tag/v1.7.20 security-advisories@github.com
- https://github.com/klever-io/klever-go/security/advisories/GHSA-26r5-4mm2-px5c security-advisories@github.com
- https://github.com/klever-io/klever-go/security/advisories/GHSA-26r5-4mm2-px5c 134c704f-9b21-4f2e-91b3-4a467353bcc0
