CVE-2026-82405
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.20, the KleverUpdateAccountPermission built-in authorizes replacement of a target account's permissions by checking attacker-controlled vmInput.RecipientAddr instead of authenticated vmInput.CallerAddr. An attacker-controlled contract can choose a victim account with configured permissions as RecipientAddr, and contractHasValidPermission can accept the victim's default self-signer as authorization. UpdatePermission can then replace the victim's entire permission set with attacker-supplied Owner permissions, enabling asset theft or permanent lockout without a victim key or signature. Accounts without stored permissions and the native transaction path are not affected. This issue is fixed in version 1.7.20.
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.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- gist.github.com/mabdullah22/a41f90aa5ba86bbebf121f739bd5f5e9
- github.com/klever-io/klever-go/commit/c58740eb74d7ee8f07db1e18a7d6214b5559ba32
- github.com/klever-io/klever-go/releases/tag/v1.7.20
- github.com/klever-io/klever-go/security/advisories/GHSA-97cv-x867-6xhm
- github.com/advisories/GHSA-97cv-x867-6xhm
- nvd.nist.gov/vuln/detail/CVE-2026-82405
- cve.org/CVERecord?id=CVE-2026-82405
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.