CVE-2026-55764
Klever-Go is the Go implementation of the Klever blockchain …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/klever-io/klever-go/commit/8bcc600b0ac88070740c63c7ce1c8a968dd85251
- github.com/klever-io/klever-go/releases/tag/v1.7.19
- github.com/klever-io/klever-go/security/advisories/GHSA-mrpp-v6pg-p54x
- github.com/advisories/GHSA-mrpp-v6pg-p54x
- nvd.nist.gov/vuln/detail/CVE-2026-55764
- cve.org/CVERecord?id=CVE-2026-55764
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.