CVE-2026-54755
Integer overflow in Klever-Go royalty split enables minting of unbacked assets.
Is CVE-2026-54755 being exploited?
Not confirmed. CVE-2026-54755 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.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-54755?
CVE-2026-54755 is rated Critical with a CVSS score of 9.6. 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-54755?
Yes. A fix has been recorded for CVE-2026-54755. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54755 affect?
CVE-2026-54755 affects Klever-Go < 1.7.19. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54755?
Upgrade to Klever-Go v1.7.19; audit payouts and suspend minting until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted royalty splits cause uint32 wrap, over-crediting payouts and allowing creation/minting of unbacked KLV or other assets (financial theft/fraud).
Immediate action required
- 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.