Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
klever-go before 1.7.20 does not escape account names when indexing them into Elasticsearch. Any funded account can set a crafted name with one transaction, which can cause indexing updates to be dropped or let an attacker create, overwrite, or delete Elasticsearch documents. Upgrade to 1.7.20.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.4 | High | 4.0 | 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 | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0034, the 27th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:12 UTC First seen by agentprime
- 31 Oct 2026, 14:12 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-7c7c-373r-gfjj
- OSV: GHSA-7c7c-373r-gfjj
- github.com/klever-io/klever-go/security/advisories/GHSA-7c7c-373r-gfjj
- github.com/klever-io/klever-go/commit/f00366768b24be18fa7ae9de2e1905caa8b350af
- github.com/klever-io/klever-go/commit/f54ea730cc80a3ba4f906586a7d221b281548190
- github.com/klever-io/klever-go
- github.com/klever-io/klever-go/releases/tag/v1.7.20