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

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

Summary

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

Original description

The description as published by the source.

Summary

The per-entry percentages of a KDA asset's split royalties are validated by summing
them into a uint32 accumulator and checking the sum against HundredPercent (10000),
with no upper bound on each individual entry. Two split entries whose percentages sum to
just over 2^32 wrap around below 10000 and pass validation, while each stored value
remains astronomically large (e.g. 0x80000000 = 2,147,483,648 ≈ 21,474,836%).

At royalty payout, each split recipient is credited pool × hugePct / 10000 — far more than
the royalty pool — and the resulting negative remainder is silently discarded
(if royaltiesToPay <= 0 { return Ok }). Because fixed royalties (and marketplace/ITO
royalties) are denominated in KLV, an attacker mints KLV (the native token) out of thin
air, on demand, by transferring or selling their own throwaway asset.

This is independent of, and not mitigated by, the existing FixMarketBuyOverflow guard.

Affected component

  • Repository: klever-io/klever-go (node).
  • Validation: core/process/kda/assetHelper.go, core/kapp/kda/create.go,
    core/kapp/kda/trigger.go, core/kapp/builtInFunctions/utils.go.
  • Payout (mint sites): core/kapp/accounts/accounts.go (transfer), core/kapp/market/market.go
    (marketplace buy), core/kapp/ito/ito.go (ITO buy).
  • Not gated by any fork flag — exploitable on current mainnet.

Root cause

1. Per-entry split percentages are decoded as raw uint32 with n…

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-54755 has been found in github.com/klever-io/klever-go.
Attackers can target a specific entry point like uint32 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-54755" on the vendor's site.

CVE-2026-54755 (github.com/klever-io/klever-go) — CWE-190 / CVSS v3 9.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: uint32 / FixMarketBuyOverflow / decodeSplitInfo / TransferPercentage
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-190) exists in github.com/klever-io/klever-go. Attackers reach the vulnerable code path via uint32.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/klever-io/klever-go. Attack surface: uint32 / FixMarketBuyOverflow / decodeSplitInfo / TransferPercentage.

🔥 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