# CVE-2026-54755: Klever-Go: Integer overflow in split-royalty validation enables unbounded minting of KLV (native token)

> Attackers can exploit an integer overflow in royalty validation to mint unbacked native tokens, affecting Klever blockchain users and operators.

- **Severity:** Critical 9.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-cgc5-v3f2-8m2v, GO-2026-6310

## What is CVE-2026-54755?

CVE-2026-54755 is a critical vulnerability in klever-io klever-go, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.19, split-royalty fields decoded in core/kapp/builtInFunctions/utils.go can contain values greater than core.HundredPercent, and core/kapp/kda/create.go and core/kapp/kda/trigger.go sum those values in uint32 accumulators. Crafted values such as two 0x80000000 entries wrap the validation sum to zero and pass CheckValid100Params. Royalty payout paths in core/kapp/accounts/accounts.go, core/kapp/market/market.go, and core/kapp/ito/ito.go then credit each oversized split amount and silently discard a negative remainder, allowing ordinary asset transfers, marketplace purchases, or ITO purchases to create unbacked KLV or other assets. This issue is fixed in version 1.7.19.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

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 | 1.7.19 |
| `github.com/klever-io/klever-go` | Go | All versions | 1.7.19 |
| `github.com/klever-io/klever-go` | Go | All versions | 1.7.19 |

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

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

## Is CVE-2026-54755 being exploited?

There is no known exploitation of CVE-2026-54755 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54755 is a critical vulnerability in klever-io klever-go, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54755 in the wild and no public exploit code.

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

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-54755/ (Markdown: https://insights.sbomify.com/CVE-2026-54755/index.md)
```

## Sources

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

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