CVE-2026-82409
Klever-Go is the Go implementation of the Klever blockchain …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/klever-io/klever-go/commit/f00366768b24be18fa7ae9de2e1905caa8b350af
- github.com/klever-io/klever-go/commit/f54ea730cc80a3ba4f906586a7d221b281548190
- github.com/klever-io/klever-go/releases/tag/v1.7.20
- github.com/klever-io/klever-go/security/advisories/GHSA-7c7c-373r-gfjj
- github.com/advisories/GHSA-7c7c-373r-gfjj
- nvd.nist.gov/vuln/detail/CVE-2026-82409
- cve.org/CVERecord?id=CVE-2026-82409
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.