Vulnerability in github.com/klever-io/klever-go (CVE-2026-55763)
Summary
Vulnerability in github.com/klever-io/klever-go (CVE-2026-55763). Risk of unauthorized operations or information disclosure. Exploitable via processPercentageRoyaltiesTransfer. Mitigation: upgrade to 1.7.19-rc4 or later.
Original description
The description as published by the source.
Summary
In processPercentageRoyaltiesTransfer the royalty pool is collected from the sender by SubFromBalance that is
ordered after the split loop and after if royaltiesToPay <= 0 { return Ok }. The split-payout guard rejects
only an allocation that exceeds the pool (a strict splitToPay > royaltiesToPay), so a split entry of exactly
100% (PercentTransferPercentage = 10000) is a valid config: it drives royaltiesToPay to 0 and hits the
early-return before the sender is debited. The split recipient keeps the full royalty; the sender pays nothing
for it → mint. The sibling fixed-royalty path (processFixedRoyaltiesTransfer) debits the sender first and is
safe. Only the percentage-transfer path collects and distributes in the same function with the collect placed after
the early-return.
Affected code
core/kapp/accounts/accounts.go—processPercentageRoyaltiesTransfer: split loop →if royaltiesToPay <= 0 { return Ok }→acntSrc.SubFromBalance(royaltyAmount)(debit after the early-return). Contrast the safe
processFixedRoyaltiesTransfer(debit before the loop).
Impact
Unbounded self-inflation of the transferred KDA: royaltyAmount = transferValue × rate is minted to an
owner-controlled split address on every transfer of the asset, with no source debit and no supply-counter update
(off-the-books).
Reachability
Owner-gated to configure (own KDA with a TransferPercentage royalty + a 100% split). Once configured, the min…
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-55763 has been found in github.com/klever-io/klever-go.
Attackers can target a specific entry point like processPercentageRoyaltiesTransfer over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/klever-io/klever-go to 1.7.19-rc4 or later.
If unsure, ask your IT team or search "github.com/klever-io/klever-go CVE-2026-55763" on the vendor's site.
CVE-2026-55763 (github.com/klever-io/klever-go) — CWE-841
Attack surface: processPercentageRoyaltiesTransfer / SubFromBalance / royaltiesToPay / processFixedRoyaltiesTransfer
Patched: 1.7.19-rc4 — 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.
A vulnerability (CWE-841) exists in github.com/klever-io/klever-go. Attackers reach the vulnerable code path via processPercentageRoyaltiesTransfer.
Check the vendor advisory for the affected versions of github.com/klever-io/klever-go. Attack surface: processPercentageRoyaltiesTransfer / SubFromBalance / royaltiesToPay / processFixedRoyaltiesTransfer.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.7.19-rc4.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/klever-io/klever-go to 1.7.19-rc4ステージング環境で 1.7.19-rc4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。