Klever-Go Marketplace Settlement Unbacked Currency Creation
CVE-2026-54754 is a critical incorrect-calculation flaw in Klever-Go marketplace settlement prior to version 1.7.19. Marketplace listings snapshot MarketOrderData.ReferralPercentage, but settlement reads the asset's royalty market percentage live. An asset owner can establish a valid listing and subsequently increase royalties through an asset royalty-update operation so that referral and royalty percentages together exceed the buyer's bid. Settlement credits referral and royalty payouts unconditionally, while the market-owner payment routine silently omits a nonpositive seller remainder. Consequently, MarketBuy, BuyItNow, and auction Claim operations can distribute more KLV or sale currency than was paid by the buyer.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
An attacker able to create and list assets can conduct self-dealing marketplace transactions or auction claims to obtain unbacked KLV or another sale currency, subject primarily to transaction fees. The resulting credits lack a corresponding debit, mint operation, or supply-accounting update, violating supply conservation and corrupting token supply integrity. The issue was reported as having been actively exploited on mainnet, including artificial NFT trading volume and subsequent conversion or bridging of illicit value.
If you can’t patch tonight, do this now.
Before the consensus fix is universally active, restrict or suspend marketplace buying, selling, marketplace creation/configuration, and royalty-update operations where operationally feasible. An emergency sender-deny guard can block known malicious accounts, but proposer-only enforcement is not consensus-enforced and depends on block-producer adoption. Monitor for listings whose referral percentage combined with current royalties exceeds the sale amount and prevent their settlement.
Patch, then assume compromise.
Upgrade all Klever-Go nodes to version 1.7.19 or later and activate the fork-gated fixMarketBuyOverflow protocol change at the network's designated activation epoch. Nodes must use the same activation epoch to prevent consensus divergence. The fix rejects marketplace settlement when referral and royalty payments would produce a negative market-owner remainder. No data migration is required. Implementations should additionally either snapshot royalty terms when a listing is created or revalidate the combined referral-and-royalty percentage at settlement, reject negative remainders, and enforce that all settlement splits exactly equal the buyer payment.
No public exploits tracked yet. Mallory keeps watching.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.