Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

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

Quick assessment

Affected
klever-io klever-go
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

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 authenti

CVSS 8.7 · High

Possible ATT&CK Techniques 1 AI

T1190 · Exploit Public-Facing Application

Affected Version Matrix 1

VendorProduct Version RangeStatus
klever-io klever-go < 1.7.20 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-82405

Vulnerability Information

Shenlong is analyzing...

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Klever-Go Account takeover: `kleverUpdateAccountPermission` authorizes on attacker-controlled `RecipientAddr` instead of the authenticated caller
Source: CVE Program / CVE List V5
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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Source: CVE Program / CVE List V5
Vulnerability Type
授权机制不正确
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
klever-io klever-go < 1.7.20 -

II. Public POCs for CVE-2026-82405

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-82405

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-82405 (1)

Other References for CVE-2026-82405 (3)

Same Patch Batch · klever-io · 2026-09-23 · 6 CVEs total

CVE-2026-86064 8.6 HIGH Klever-Go: /log controls global node logging
CVE-2026-82409 8.4 HIGH Klever-Go: Elasticsearch bulk / painless injection via on-chain account name -> explorer/
CVE-2026-86065 7.5 HIGH Klever-Go: Unauthenticated WebSocket /subscribe: no read-size limit, no connection cap, pe
CVE-2026-82406 7.1 HIGH Klever-Go: Zombie-order theft: `Buy` missing `IsClaimed` guard in native marketplace
CVE-2026-82407 7.0 HIGH Klever-Go: Validator registration accepts an unvalidated BLS public key → consensus livene

IV. Related Vulnerabilities

Same product: klever-go
Same vendor: klever-io
Same weakness: CWE-863

V. Comments for CVE-2026-82405

No comments yet

Leave a comment