Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-54754 critical CVSS 9.6

Vulnerability in github.com/klever-io/klever-go (CVE-2026-54754)

Summary

Vulnerability in github.com/klever-io/klever-go (CVE-2026-54754). Data can be tampered with by attackers. Exploitable via MarketBuy. Mitigation: upgrade to 1.7.19 or later.

Original description

The description as published by the source.

Summary

When a marketplace order is settled (MarketBuy / BuyItNow, and auction Claim), the buyer's
payment is split three ways — referral, royalties, and the seller (market-order owner)
remainder:

marketOwnerAmount = CurrentBid − referralAmount − royaltiesAmount

Referral and royalties are paid out unconditionally, but the seller remainder is only paid
when positive (computeMarketOwnerAmount returns Ok and pays nothing when the amount is
<= 0). When referral% + royalty% exceeds 100% of the bid, marketOwnerAmount goes negative
and is silently skipped — so the marketplace pays out more KLV / sale currency than the buyer
paid in, minting the difference out of thin air.

The combined ceiling royalty% + referral% <= 100% is checked once, at listing time (Sell).
But the two percentages are sourced asymmetrically at settlement:

  • referral % is snapshotted into the order at Sell (MarketOrderData.ReferralPercentage);
  • royalty % is never snapshotted — it is read live from the asset at buy time
    (asset.Royalties.MarketPercentage).

So the listing-time invariant is a time-of-check/time-of-use guarantee only. After a valid
listing, the asset owner raises the royalty MarketPercentage via AssetTrigger → UpdateRoyalties;
at the next buy the live royalty plus the snapshotted referral exceed 100%, and the settlement mints
the overflow. The minted funds land in attacker-controlled referral / ro…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-54754 has been found in github.com/klever-io/klever-go.
Attackers can target a specific entry point like MarketBuy over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 9.6/10.
What to do: upgrade github.com/klever-io/klever-go to 1.7.19 or later.
If unsure, ask your IT team or search "github.com/klever-io/klever-go CVE-2026-54754" on the vendor's site.

CVE-2026-54754 (github.com/klever-io/klever-go) — CWE-191 / CVSS v3 9.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: MarketBuy / BuyItNow / Claim / computeMarketOwnerAmount
Patched: 1.7.19 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-191) exists in github.com/klever-io/klever-go. Attackers reach the vulnerable code path via MarketBuy.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/klever-io/klever-go. Attack surface: MarketBuy / BuyItNow / Claim / computeMarketOwnerAmount.

🔥 Severity

Severity: Critical (CVSS 9.6/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 1.7.19.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/klever-io/klever-go' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/klever-io/klever-go' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/klever-io/klever-go を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/klever-io/klever-go to 1.7.19

    ステージング環境で 1.7.19 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/klever-io/klever-go
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.7.19"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details