Skip to content
skopnix

NVD published 23 Sep 2026

CVE-2026-82409

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.

Signals

KEV, exploited in the wild
no
EPSS, 30-day forecast
0.3%, 28th percentile (as of 18 Nov 2026)
CVSS, NVD
not stated
Internet exposure
not stated

Not in CISA's catalogue as of the last daily pull. Absence is not proof of safety. No score published by NVD.

Indicators none tied yet

No threat feed has tied an indicator to this CVE yet. Checked every six hours.

On the wire 1 dispatch

  1. GHSA-7c7c-373r-gfjj: Klever-Go: Elasticsearch bulk / painless injection via on-chain account name -> explorer/indexer data forgery

Public exploit code none in our sources

No public exploit in the sources we track: GitHub proof-of-concept lists, Metasploit and Exploit-DB. Absence is not proof that none exists.

References

Watch this one?

KEV additions reach Telegram and the KEV-only RSS as they land.

Telegram ↗KEV RSSAPIStack check