CVE-2026-54755

Received Received - Intake

Integer Overflow in Klever-Go Blockchain Protocol

Publication date: 2026-08-28

Last updated on: 2026-08-28

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-28

Last Modified

2026-08-28

Generated

2026-08-29

AI Q&A

2026-08-29

EPSS Evaluated

N/A

NVD

CVE-2026-54755

EUVD

EUVD-2026-67825

Affected Vendors & Products

Vendor	Product	Version / Range
klever	klever-go	1.7.19

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-190	The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

Attack-Flow Graph

Executive Summary

This vulnerability is an integer overflow flaw in the Klever blockchain's Go implementation (klever-go). It allows attackers to mint unlimited KLV tokens by exploiting how split royalty percentages are validated. When two large split entries sum to over 2^32, they wrap around to appear valid, crediting recipients with inflated amounts while discarding negative remainders. This bypasses supply tracking and creates unbacked tokens.

Detection Guidance

To detect this vulnerability, monitor for transactions involving split-royalty operations that result in invalid royalty payouts or unexpected asset creation. Check logs for transactions where royalty sums exceed 100% or where negative remainders are discarded. Review RPC endpoint logs for `/transaction/send` requests with oversized split values.

Impact Analysis

If you use the Klever blockchain, an attacker could exploit this to inflate the KLV supply, devaluing your holdings. Transactions like asset transfers or marketplace purchases could silently create unbacked tokens, disrupting the network's integrity. Exploitation requires only a funded account and access to the /transaction/send RPC endpoint.

Mitigation Strategies

Immediately upgrade to Klever-Go version 1.7.19 or later. Implement input validation to reject split-royalty percentages exceeding 100%. Use uint64 for validation sums to prevent overflow. Treat negative royalty remainders as errors and discard transactions that fail validation.

Hi! I’m here to help you understand CVE-2026-54755. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70