Vulnerability Description
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.
Related Weaknesses (CWE)
References
- https://gist.github.com/mabdullah22/a41f90aa5ba86bbebf121f739bd5f5e9
- https://github.com/klever-io/klever-go/commit/c58740eb74d7ee8f07db1e18a7d6214b55
- https://github.com/klever-io/klever-go/releases/tag/v1.7.20
- https://github.com/klever-io/klever-go/security/advisories/GHSA-97cv-x867-6xhm
FAQ
What is CVE-2026-82405?
CVE-2026-82405 is a documented vulnerability. 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 a...
How severe is CVE-2026-82405?
CVSS scoring is not yet available for CVE-2026-82405. Check NVD for updates.
Is there a patch for CVE-2026-82405?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.