Klever-Go: Elasticsearch bulk / painless injection via on-chain account name -> explorer/indexer data forgery
Historical advisory recorded 23 Oct 2026 15:48:27 UTC. Read the latest advisory.
cve-program · CVE-2026-82409
PublishedKlever-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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-82409 · CVE overview and exploitation status
cve-program · CVE-2026-82409
- https://github.com/klever-io/klever-go/security/advisories/GHSA-7c7c-373r-gfjj
- https://github.com/klever-io/klever-go/commit/f00366768b24be18fa7ae9de2e1905caa8b350af
- https://github.com/klever-io/klever-go/commit/f54ea730cc80a3ba4f906586a7d221b281548190
- https://github.com/klever-io/klever-go/releases/tag/v1.7.20
This historical advisory does not include today's related changes. Open the latest advisory to find current connections.