CVE-2026-55763

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

Published Aug 28, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Klever-Go's percentage‑transfer royalty function contains a logic error that allows a 100 % split to skip debiting the source account after royalties are exhausted. The function computeSplitRoyalties permits a split of exactly the entire royalty pool; the subsequent early return occurs before SubFromBalance is invoked on the source, leaving the sender's balance unchanged while the recipient receives the full royalty amount. The global supply counter likewise is not updated, creating a mechanism for unbounded off‑the‑books minting of KDA.

Affected Systems

All installations of Klever-Go released before version 1.7.19 are affected. The vulnerability is specific to the Klever‑IO blockchain implementation, and impacts any KDA holder who has configured a TransferPercentage royalty with a 100 % split. The fix is distributed in release 1.7.19, which corrects the transfer logic.

Risk and Exploitability

The vulnerability scores a CVSS of 8.7, indicating high severity. EPSS is not available, but the flaw can be exercised by any actor who initiates a token transfer that triggers a 100 % royalty split, a situation that many owners may have configured. The bug is listed as non‑exploited in the CISA KEV catalog; however, because it enables the minting of new tokens without source debits, the potential impact on token economics is significant.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Klever-Go to version 1.7.19 or newer.
  • Reconfigure TransferPercentage royalties so that no split consumes 100 % of the royalty pool; set split percentages below 100 % or disable royalties.
  • Monitor token transfer logs for unexpected minting events and audit supply changes.

Generated by OpenCVE AI on August 28, 2026 at 23:50 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-v358-wf77-39xv klever-go: Percentage-transfer royalty skips the source debit at exactly-100% splits
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Klever-io
Klever-io klever-go
Vendors & Products Klever-io
Klever-io klever-go
Type Values Removed Values Added
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.
Title Klever-Go: Percentage-transfer royalty skips the source debit at exactly-100% splits
Weaknesses CWE-841
References
Metrics cvssV4_0

{'score': 8.7, 'vector': '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'}

Weaknesses
  • CWE-841

    Improper Enforcement of Behavioral Workflow

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 31, 2026, 2:02 PM
Reserved
Jun 17, 2026, 2:34 PM
Status
Deferred
Published
Aug 28, 2026, 10:16 PM
Modified
Sep 9, 2026, 9:09 PM