CVE-2026-55763

High

Description

Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.19, processPercentageRoyaltiesTransfer in core/kapp/accounts/accounts.go calls SubFromBalance after the split loop and after the royaltiesToPay <= 0 early return. computeSplitRoyalties rejects only when splitToPay > royaltiesToPay, so a valid PercentTransferPercentage = 10000 split consumes exactly 100 percent of the royalty pool, sets royaltiesToPay to zero, and returns before the source account is debited. The split recipient receives the full royaltyAmount while the sender pays nothing and the supply counter is not updated, allowing unbounded off-the-books inflation of the transferred KDA. A KDA owner must configure a TransferPercentage royalty with a 100 percent split, after which any holder's transfer of the asset triggers the mint; the sibling processFixedRoyaltiesTransfer path is not affected because it debits the source before distribution. This issue is fixed in version 1.7.19.

SeverityHigh
CVSS8.7
Exploit probability—
ProductGithub.com/klever-io/klever-go
PublishedAug 28, 2026
First seenAug 28, 2026
Weakness typeCWE-841CWE-841

How to fix

Update
  • github.com/klever-io/klever-go1.7.19-rc4 or later

Affected products

ProductAffected versionsFixed in
github.com/klever-io/klever-goGov < 1.7.19-rc4, No range specified1.7.19-rc4

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.

CVE-2026-55763 · Github.com/klever-io/klever-go · Dark Radar