CVE-2026-55763
Klever-Go bug allows minting unlimited KDA via 100% royalty split.
Is CVE-2026-55763 being exploited?
Not confirmed. CVE-2026-55763 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-55763?
CVE-2026-55763 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-55763?
Yes. A fix has been recorded for CVE-2026-55763. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-55763 affect?
CVE-2026-55763 affects klever-go < 1.7.19, Klever blockchain nodes, KDA token ledgers, wallets interacting with KDA. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-55763?
Upgrade to klever-go v1.7.19; remove 100% royalties; audit and reconcile KDA supply.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
An attacker configuring a 100% transfer royalty can trigger transfers that mint unbounded KDA (off‑books inflation), corrupting token supply and ledgers.
Patch when possible
- affected< 1.7.19
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.