Live › vulnerability › CVE-2026-82409
Go to dashboardKlever-Go, the Go implementation of the Klever blockchain, does not escape account names when writing them into Elasticsearch bulk requests. An attacker who sets an account name containing quotes or newlines via a SetAccountName transaction can inject extra bulk actions that create, overwrite, or delete documents in indices the indexer can write to.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| github.com/klever-io/klever-go | go | < 1.7.20 | 1.7.20 |
Check the go.mod of your Klever-Go deployment for github.com/klever-io/klever-go and confirm the version is below 1.7.20.
1.7.20 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-82409")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.