CVE-2026-82409

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (27th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-85647 (ENISA EUVD) · GHSA-7c7c-373r-gfjj (GitHub Security Advisories) · GO-2026-6585 (OSV.dev)Source: ENISA EUVD

8.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.4Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
54
EG Risk 54/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity84% × 45%
Impact severity (EG Severity): CVSS 8.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
27th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is its impact severity (EG Severity), not escalated.

EG Severity
8.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 23, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Sep 23, 2026
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 advisoryMentions a patch (unverified)

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.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/klever-io/klever-go @ 1.7.20 (fixes <= 1.7.19)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/klever-io/klever-go—
  • every version up to 1.7.20: fixed in 1.7.20
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-11-11 18:13 UTCEchelonGraph re-scored
  3. 2026-11-11 18:12 UTCGHSA enrichmentGHSA-7c7c-373r-gfjj · GitHub severity HIGH
  4. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  5. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  6. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  7. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  8. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  9. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  10. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  11. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  12. 2026-11-04 12:17 UTCEchelonGraph re-scored
  13. 2026-11-04 12:17 UTCGHSA enrichmentGHSA-7c7c-373r-gfjj · GitHub severity HIGH
  14. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  15. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  16. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  17. 2026-11-01 07:38 UTCGHSA enrichmentGHSA-7c7c-373r-gfjj · GitHub severity HIGH
  18. 2026-11-01 07:38 UTCEchelonGraph re-scored
  19. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  20. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  21. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  22. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  23. 2026-10-28 06:39 UTCEchelonGraph re-scored
  24. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  25. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
Show 60 more
  1. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-10-25 13:58 UTCEchelonGraph re-scored
  3. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  4. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  5. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  6. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  7. 2026-10-20 18:03 UTCEchelonGraph re-scored
  8. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  9. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  10. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  11. 2026-10-18 03:08 UTCEchelonGraph re-scored
  12. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  13. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  14. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  15. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  16. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  17. 2026-10-13 06:03 UTCEchelonGraph re-scored
  18. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  19. 2026-10-12 14:55 UTCEchelonGraph re-scored
  20. 2026-10-11 19:19 UTCEchelonGraph re-scored
  21. 2026-10-11 16:36 UTCEchelonGraph re-scored
  22. 2026-10-11 13:54 UTCEchelonGraph re-scored
  23. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  24. 2026-10-10 23:51 UTCEchelonGraph re-scored
  25. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  26. 2026-10-10 02:10 UTCEchelonGraph re-scored
  27. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  28. 2026-10-09 04:02 UTCEchelonGraph re-scored
  29. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  30. 2026-10-08 06:21 UTCEchelonGraph re-scored
  31. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  32. 2026-10-06 21:48 UTCEchelonGraph re-scored
  33. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  34. 2026-10-06 00:08 UTCEchelonGraph re-scored
  35. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  36. 2026-10-05 02:18 UTCEchelonGraph re-scored
  37. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  38. 2026-10-03 17:46 UTCEchelonGraph re-scored
  39. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  40. 2026-10-02 20:05 UTCEchelonGraph re-scored
  41. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  42. 2026-10-01 22:24 UTCEchelonGraph re-scored
  43. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  44. 2026-10-01 00:38 UTCEchelonGraph re-scored
  45. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  46. 2026-09-29 16:05 UTCEchelonGraph re-scored
  47. 2026-09-29 05:13 UTCEchelonGraph re-scored
  48. 2026-09-28 18:23 UTCEchelonGraph re-scored
  49. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  50. 2026-09-27 20:39 UTCEchelonGraph re-scored
  51. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  52. 2026-09-26 22:58 UTCEchelonGraph re-scored
  53. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  54. 2026-09-26 01:17 UTCEchelonGraph re-scored
  55. 2026-09-24 16:37 UTCEchelonGraph re-scored
  56. 2026-09-24 15:32 UTCEchelonGraph re-scored
  57. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  58. 2026-09-23 20:22 UTCEchelonGraph re-scored
  59. 2026-09-23 19:29 UTCEchelonGraph re-scoredFirst assessed: 8.4 HIGH
  60. 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-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-82409 published?
The CVE record for CVE-2026-82409 was published on September 23, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-82409 actively exploited?
CVE-2026-82409 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82409?
CVE-2026-82409 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82409?
A fix for CVE-2026-82409 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-82409 are linked in the Vendor Advisories panel on this page.

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