Live › vulnerability › CVE-2026-82405
Go to dashboardKlever-Go, the Go implementation of the Klever blockchain protocol, has an authorization bug in its KleverUpdateAccountPermission built-in: it checks the attacker-controlled RecipientAddr instead of the authenticated CallerAddr. An attacker-controlled contract can replace a victim account's entire permission set without the victim's key, enabling asset theft or permanent lockout.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| github.com/klever-io/klever-go | go | < 1.7.20 | 1.7.20 |
Check whether go.mod pins github.com/klever-io/klever-go below 1.7.20 (grep klever-go go.mod).
Upgrade github.com/klever-io/klever-go to 1.7.20 or later.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-82405")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.