CVE-2026-55763
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Low risk: more likely to be exploited than 23% of all known CVEs.
References
Related Vulnerabilities
Other CWE-841 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2022-1667 | High | 7.5 | 1.2% | - | Fix |
| CVE-2023-4181 | Medium | 5.4 | 1.1% | - | - |
| CVE-2022-2105 | Critical | 9.4 | 1.1% | - | Fix |
| CVE-2022-2102 | Critical | 9.4 | 0.9% | - | Fix |
| CVE-2024-51738 | High | 8.1 | 0.6% | - | Fix |
| CVE-2024-37296 | Medium | 5.3 | 0.5% | - | - |
Common questions
How do I fix CVE-2026-55763?
No published fix for CVE-2026-55763 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-55763 being actively exploited?
Not that we know of. CVE-2026-55763 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.30% is the estimated probability that it will be exploited in the next 30 days. That is higher than 23% of all scored CVEs.
How severe is CVE-2026-55763?
CVE-2026-55763 has a CVSS v4 base score of 8.7, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-55763
Markdown
[](https://tridentstack.com/cve/CVE-2026-55763)HTML
<a href="https://tridentstack.com/cve/CVE-2026-55763"><img src="https://tridentstack.com/cve/badge/CVE-2026-55763.svg" alt="CVE-2026-55763"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-28.