Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, the native marketplace function core/kapp/market/market.go Buy does not check IsClaimed before accepting a bid. A seller can use the Claim seller-accept branch to settle a resting-bid auction while leaving the claimed order loadable with a future EndTime and stale CurrentBid and CurrentBidder values. A later bidder can submit a higher bid, be debited, and cause the previous bidder to receive a refund even though the NFT has already been delivered. Because Claim and CancelOrder reject the later bidder when IsClaimed is true, the later bidder cannot obtain the NFT or recover the funds. This issue is fixed in version 1.7.20.
CVE-2026-82406
HIGHPre-NVD 7.17.1—Trending — 3 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% 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).
Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: Elevated riskExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.1
- EG Score
- 7.1(medium)
- EG Risk
- 48(Track)EG Risk 48/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 computedSeverity71% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 25%
- KEV
- Not listed
Published
September 23, 2026
Last Modified
September 24, 2026
Advisory Details (4)
Auto-updated Sep 23, 2026🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available
v1.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.20github_commit Patch Available
commit 063bb3ed98f9 (klever-io/klever-go)
Patch available: klever-io/klever-go v1.7.20 (contains commit 063bb3ed98f9)
https://github.com/klever-io/klever-go/commit/063bb3ed98f9a84a4b1f7286680613a5fc3c91b2github_pr Patch Available
[KLC-1974] feat(validators): implement V2 epoch rewards distribution
Patch available: klever-io/klever-go v1.7.16 (PR #16 merged 2025-12-01)
https://github.com/klever-io/klever-go/pull/16github Patch Available🟡 PoC Available
Zombie-order theft: `Buy` missing `IsClaimed` guard in native marketplace · Advisory · klever-io/klever-go · GitHub
https://github.com/klever-io/klever-go/security/advisories/GHSA-26r5-4mm2-px5cVendor Advisories for CVE-2026-82406(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 6× in last 7d / 6× 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 15:32 UTCEG score recompute
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 20:22 UTCEG score recompute
- 2026-09-23 19:19 UTCEG score recompute
- 2026-09-23 19:19 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-82406?
CVE-2026-82406 is a high vulnerability published on September 23, 2026. Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, the native marketplace function core/kapp/market/market.go Buy does not check IsClaimed before accepting a bid. A seller can use the Claim seller-accept branch to settle a resting-bid auction while leaving the…
When was CVE-2026-82406 disclosed?
CVE-2026-82406 was first published in the National Vulnerability Database on September 23, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82406 actively exploited?
CVE-2026-82406 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 75.1% of all scored CVEs.
What is the CVSS score of CVE-2026-82406?
CVE-2026-82406 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-82406?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82406, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-82406
Is Your Infrastructure Affected by CVE-2026-82406?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.