CVE-2026-55764

published 28 Aug 2026 · updated 31 Aug 2026

Klever-Go: SFT add-quantity `int64` overflow bypasses a finite per-nonce MaxSupply

8.7HighCVSS 8.7EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. No fixed version is recorded.

Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.19, Klever-Go allows a mint-role holder to bypass a finite per-nonce MaxSupply on the semi-fungible token add-quantity path. In core/kapp/systemAccount/systemAcount.go, SFTAddCirculation performed meta.Circulation += amount before evaluating whether Circulation exceeded MaxSupply, without checking for signed int64 overflow. A large positive raw Amount supplied through processSemiFungibleAddQuantity in core/kapp/kda/mint.go can wrap Circulation negative, causing the signed maximum-supply comparison to pass and crediting approximately MaxInt64 units while corrupting the on-chain counter. The fungible path is not affected because its MintedValue <= 0 guard detects the overflow. The correction uses the consensus activation flag FixMarketBuyOverflow. This issue is fixed in version 1.7.19.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
klever-io<1.7.19

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-55764 severity on Zeptric[![CVE-2026-55764](https://zeptric.io/badge/cve/CVE-2026-55764.svg)](https://zeptric.io/cve/CVE-2026-55764)