Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-82409

Vulnerability in github.com/klever-io/klever-go (CVE-2026-82409)

Summary

Vulnerability in github.com/klever-io/klever-go (CVE-2026-82409). Risk of unauthorized operations or information disclosure. Exploitable via serializedDataForUpdateAccounts. Mitigation: upgrade to 1.7.20 or later.

Original description

The description as published by the source.

Component: Elasticsearch indexer (indexer/)
Primary location: indexer/common.go:2395-2407 (serializedDataForUpdateAccounts)
Entry point: SetAccountName native transaction (contract type 12) — core/process/transaction/txProcess.go:688

Description

When the node indexes account updates to Elasticsearch, it builds the ES _bulk painless-script line by splicing the account's name directly into JSON with fmt.Sprintf("%s", ...) and no escaping:

// indexer/common.go:2395-2407  (serializedDataForUpdateAccounts)
serializedData := []byte(fmt.Sprintf(`{"script":{"source":"`+
    `ctx._source.name = params.name; ... `+
    `","lang": "painless","params":`+
    `{"name": "%s", "nonce": %d, "rootHash": "%s", "balance": %d, ...}}}`,
    acc.Name, acc.Nonce, acc.RootHash, acc.Balance, ...))   // acc.Name is RAW

acc.Name originates from on-chain account state: indexer/accountInfo.go:31 sets Name: string(userAccount.GetName()). An account name is fully attacker-controlled and only weakly validated when it is set on-chain by the SetAccountName handler:

// core/kapp/accounts/accounts.go:1740
if !utf8.Valid(tc.GetName()) || len(tc.GetName()) > core.MaxNameSize { ... }  // MaxNameSize = 100

The only constraints are valid UTF-8 and length ≤ 100 bytes. Double-quote ("), backslash (\), and newline (\n) are all valid UTF-8 and are not rejected. The safe helper converters.JsonEscape() exists and is used for `_…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-82409 has been found in github.com/klever-io/klever-go.
Attackers can target a specific entry point like serializedDataForUpdateAccounts over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/klever-io/klever-go to 1.7.20 or later.
If unsure, ask your IT team or search "github.com/klever-io/klever-go CVE-2026-82409" on the vendor's site.

CVE-2026-82409 (github.com/klever-io/klever-go) — CWE-116
Attack surface: serializedDataForUpdateAccounts / SetAccountName / _bulk / acc.Name
Patched: 1.7.20 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-116) exists in github.com/klever-io/klever-go. Attackers reach the vulnerable code path via serializedDataForUpdateAccounts.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/klever-io/klever-go. Attack surface: serializedDataForUpdateAccounts / SetAccountName / _bulk / acc.Name.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.7.20.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/klever-io/klever-go' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/klever-io/klever-go' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/klever-io/klever-go を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/klever-io/klever-go to 1.7.20

    ステージング環境で 1.7.20 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/klever-io/klever-go
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.7.20"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details