Advisory record · GHSA-7c7c-373r-gfjj

Klever-Go: Elasticsearch bulk / painless injection via on-chain account name -> explorer/indexer data forgery

CVSS 8.4 HighEPSS 0.0034 · 27th percentile

Published by the GitHub Advisory Database at 23 Sept 2026, 21:24 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/klever-io/klever-goGo<1.7.201.7.20
Identifiers
GHSA-7c7c-373r-gfjj · CVE-2026-82409 · GO-2026-6585
Weakness (CWE)
CWE-116
Published
23 Sept 2026
Updated
1 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

klever-go before 1.7.20 does not escape account names when indexing them into Elasticsearch. Any funded account can set a crafted name with one transaction, which can cause indexing updates to be dropped or let an attacker create, overwrite, or delete Elasticsearch documents. Upgrade to 1.7.20.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.4 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0034, the 27th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:12 UTC First seen by agentprime
  2. 31 Oct 2026, 14:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.