CVE-2026-82409

HIGHPre-NVD 8.48.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% 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
Trending — 3 sources updated this weekElevated
8.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.4Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.20, indexer/common.go serializedDataForUpdateAccounts places the attacker-controlled acc.Name value into an Elasticsearch _bulk JSON and NDJSON request without escaping it. The SetAccountName transaction accepts valid UTF-8 account names containing quotes, backslashes, and newlines, and the resulting name is stored in consensus account state. When an indexer processes the account, those characters can break the JSON string, reject a bulk batch, or inject additional bulk actions that create, overwrite, or delete documents in indices writable by the indexer. The persistent state value is replayed by new or historical indexers, and direct access to the indexing host or Elasticsearch port is not required. This issue is fixed in version 1.7.20.

CVSS v3
8.4
EG Score
8.4(medium)
EG Risk
54(Track)
EG Risk 54/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 computed
Severity84% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
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_release, github, github_commit.
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.20
github_commit Patch Available

commit f54ea730cc80 (klever-io/klever-go)

Patch available: klever-io/klever-go v1.7.20 (contains commit f54ea730cc80)

https://github.com/klever-io/klever-go/commit/f54ea730cc80a3ba4f906586a7d221b281548190
github_commit Patch Available

commit f00366768b24 (klever-io/klever-go)

Patch available: klever-io/klever-go v1.7.20 (contains commit f00366768b24)

https://github.com/klever-io/klever-go/commit/f00366768b24be18fa7ae9de2e1905caa8b350af
github Patch Available🟡 PoC Available

Elasticsearch bulk / painless injection via on-chain account name -> explorer/indexer data forgery · Advisory · klever-io/klever-go · GitHub

https://github.com/klever-io/klever-go/security/advisories/GHSA-7c7c-373r-gfjj

Vendor Advisories for CVE-2026-82409(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)
PackageVulnerable rangeFixed inDependents
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.

  1. 2026-09-24 16:37 UTCEG score recompute
  2. 2026-09-24 15:32 UTCEG score recompute
  3. 2026-09-24 14:04 UTCEPSS rescore
  4. 2026-09-23 20:22 UTCEG score recompute
  5. 2026-09-23 19:29 UTCEG score recompute
  6. 2026-09-23 19:29 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-82409?
CVE-2026-82409 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, indexer/common.go serializedDataForUpdateAccounts places the attacker-controlled acc.Name value into an Elasticsearch _bulk JSON and NDJSON request without escaping it. The SetAccountName transaction accepts…
When was CVE-2026-82409 disclosed?
CVE-2026-82409 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-82409 actively exploited?
CVE-2026-82409 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 83.2% of all scored CVEs.
What is the CVSS score of CVE-2026-82409?
CVE-2026-82409 has a CVSS v3 base score of 8.4 (NVD).
How do I remediate CVE-2026-82409?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82409, 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-82409

Explore →

Is Your Infrastructure Affected by CVE-2026-82409?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs