# CVE-2026-55763: Klever-Go: Percentage-transfer royalty skips the source debit at exactly-100% splits

> Attackers can mint unlimited tokens by configuring a 100% royalty split, bypassing source account debits in the Klever-Go blockchain implementation.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-v358-wf77-39xv, GO-2026-6323

## What is CVE-2026-55763?

CVE-2026-55763 is a high-severity vulnerability in klever-io klever-go, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-841 (Improper Enforcement of Behavioral Workflow)

## Which versions are affected by CVE-2026-55763?

3 open source packages ship an affected version, including github.com/klever-io/klever-go.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/klever-io/klever-go` | Go | All versions | None |
| `github.com/klever-io/klever-go` | Go | All versions | 1.7.19-rc4 |
| `github.com/klever-io/klever-go` | Go | All versions | 1.7.19-rc4 |

## How do I fix CVE-2026-55763?

Upgrade github.com/klever-io/klever-go to 1.7.19-rc4 or later.

## Is CVE-2026-55763 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55763 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-55763 and fix it if it is affected.

What it is: CVE-2026-55763 is a high-severity vulnerability in klever-io klever-go, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55763 exists.

Affected packages and fixed versions:
- github.com/klever-io/klever-go (Go): affected all versions; no fix listed
- github.com/klever-io/klever-go (Go): affected all versions; fixed in 1.7.19-rc4
- github.com/klever-io/klever-go (Go): affected all versions; fixed in 1.7.19-rc4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-55763/ (Markdown: https://insights.sbomify.com/CVE-2026-55763/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-55763
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-55763
- OSV: https://osv.dev/vulnerability/CVE-2026-55763

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-55763/
Summaries are generated and may contain mistakes; the official description above is the record.