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.
CVE-2026-82405
This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.7
- EG Score
- 8.7(medium)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity87% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 16%
- KEV
- Not listed
Published
September 23, 2026
Last Modified
September 24, 2026
Advisory Details (4)
Auto-updated Sep 23, 2026v1.7.20 - CertiK Audit Remediation & Coordinated Security Release
Patch available: klever-io/klever-go v1.7.20
https://github.com/klever-io/klever-go/releases/tag/v1.7.20Account takeover POC · GitHub
https://gist.github.com/mabdullah22/a41f90aa5ba86bbebf121f739bd5f5e9commit c58740eb74d7 (klever-io/klever-go)
Patch available: klever-io/klever-go v1.7.20 (contains commit c58740eb74d7)
https://github.com/klever-io/klever-go/commit/c58740eb74d7ee8f07db1e18a7d6214b5559ba32Account takeover: `kleverUpdateAccountPermission` authorizes on attacker-controlled `RecipientAddr` instead of the authenticated caller · Advisory · klever-io/klever-go · GitHub
https://github.com/klever-io/klever-go/security/advisories/GHSA-97cv-x867-6xhmVendor Advisories for CVE-2026-82405(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Go(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/klever-io/klever-go | — | 1.7.20 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-24 16:37 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 20:22 UTCEG score recompute
- 2026-09-23 19:29 UTCEG score recompute
- 2026-09-23 19:29 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownGo:github.com/klever-io/klever-go
Frequently asked(5)
What is CVE-2026-82405?
When was CVE-2026-82405 disclosed?
Is CVE-2026-82405 actively exploited?
What is the CVSS score of CVE-2026-82405?
How do I remediate CVE-2026-82405?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-82405
Is Your Infrastructure Affected by CVE-2026-82405?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.