Vulnerability in github.com/klever-io/klever-go (CVE-2026-46403)
Summary
Vulnerability in github.com/klever-io/klever-go (CVE-2026-46403). Data can be tampered with by attackers. Exploitable via develop. Mitigation: upgrade to 1.7.17 or later.
Original description
The description as published by the source.
Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.17, KVM exposes ExecuteReadOnlyWithTypedArguments as a read-only execution mechanism. The hook saves the previous read-only state, sets runtime.SetReadOnly(true), executes the destination context, and then restores the previous read-only state. However, the indirect contract delete and upgrade paths do not reject execution when runtime.ReadOnly() is true. As a result, a contract reached through read-only execution can call the production delete hook for a target contract it owns. The delete path appends the target address to vmOutput.DeletedAccounts, the output context merges DeletedAccounts into the caller output, and the smart contract processor later processes the VM output by deleting accounts listed in that field. The root cause is that read-only mode is applied as runtime state, but not enforced by the state-changing delete and upgrade host-core paths. This breaks the expected isolation boundary for workflows that rely on read-only calls to inspect another contract without allowing that callee to produce state-changing VM output. The issue is fixed in v1.7.17. Contract delete and upgrade host-core paths now reject execution when runtime.ReadOnly() is true. The invariant is regression-tested for delete, upgrade, storage writes, value transfers, and any VM output field that can later mutate chain state.
Source: GitHub Security Advisories (Global) 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-46403 has been found in github.com/klever-io/klever-go.
Attackers can target a specific entry point like develop over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.3/10.
What to do: upgrade github.com/klever-io/klever-go to 1.7.17 or later.
If unsure, ask your IT team or search "github.com/klever-io/klever-go CVE-2026-46403" on the vendor's site.
CVE-2026-46403 (github.com/klever-io/klever-go) — CWE-693 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: develop / ExecuteReadOnlyWithTypedArguments / vmOutput.DeletedAccounts / DeletedAccounts
Patched: 1.7.17 — 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.
A vulnerability (CWE-693) exists in github.com/klever-io/klever-go. Attackers reach the vulnerable code path via develop.
Check the vendor advisory for the affected versions of github.com/klever-io/klever-go. Attack surface: develop / ExecuteReadOnlyWithTypedArguments / vmOutput.DeletedAccounts / DeletedAccounts.
Severity: Medium (CVSS 6.3/10). Data can be tampered with by attackers.
Update to 1.7.17.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
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
-
1Identify 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 し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/klever-io/klever-go to 1.7.17ステージング環境で 1.7.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com