Skip to content
OpenAdvisories
High · 8.7 CVE-2026-82405 EUVD-2026-85648GHSA-97cv-x867-6xhmGO-2026-6582

Klever-Go Account takeover: `kleverUpdateAccountPermission` authorizes on attacker-controlled `RecipientAddr` instead of the authenticated caller

Published Sep 23, 2026 · Updated Sep 24, 2026 · Assigned by GitHub_M

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.

Affected products

VendorProductAffectedFixed
klever-io klever-go < 1.7.20 —

Affected packages

EcosystemPackageAffectedFixedRecord
Go github.com/klever-io/klever-go < 1.7.20 1.7.20 GHSA-97cv-x867-6xhm

References