CVE-2026-82409
HIGHDescription
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.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v4 Vector
Exploitability
Impact
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Exploit Intelligence
Low risk: more likely to be exploited than 18% of all known CVEs.
References
Related Vulnerabilities
Other CWE-116 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-38475 | Critical | 9.1 | 100% | KEV | Fix |
| CVE-2022-36446 | Critical | 9.8 | 96% | - | Fix |
| CVE-2021-31806 | Medium | 6.5 | 95% | - | Fix |
| CVE-2022-30781 | High | 7.5 | 88% | - | Fix |
| CVE-2022-36099 | Critical | 9.9 | 76% | - | Fix |
| CVE-2022-36100 | Critical | 9.9 | 74% | - | Fix |
Common questions
How do I fix CVE-2026-82409?
No published fix for CVE-2026-82409 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-82409 being actively exploited?
Not that we know of. CVE-2026-82409 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.27% is the estimated probability that it will be exploited in the next 30 days. That is higher than 18% of all scored CVEs.
How severe is CVE-2026-82409?
CVE-2026-82409 has a CVSS v4 base score of 8.4, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-82409
Markdown
[](https://tridentstack.com/cve/CVE-2026-82409)HTML
<a href="https://tridentstack.com/cve/CVE-2026-82409"><img src="https://tridentstack.com/cve/badge/CVE-2026-82409.svg" alt="CVE-2026-82409"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-24.