Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-54754: Klever-Go Marketplace Settlement Unbacked Currency Creation

Published Aug 28, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.6Critical · v3.1
EPSS0.43%38th percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
IdentifiersCVE-2026-54754CWE-682 · Incorrect Calculation

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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.

Mitigation

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.

Remediation

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-54754 exploited in the wild?
Yes. As of Sep 25, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-54754?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-54754.
Is there a patch for CVE-2026-54754?
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.
How severe is CVE-2026-54754?
CVE-2026-54754 has a CVSS v3.1 score of 9.6 (Critical) and an EPSS score of 0.43% (38th percentile) as of Sep 25, 2026.
Activity feed

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.