Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CVE-2026-46403— Klever-Go KVM read-only execution can commit contract delete and upgrade side effects

Quick assessment

Affected
klever-io klever-go
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

klever-go是 klever-io klever-go 1.7.17之前版本存在处理逻辑错误漏洞,该漏洞源于间接合约删除和升级路径未在只读模式下拒绝执行,破坏了隔离边界,可能导致合同通过只读执行调用删除钩子,产生状态变更的VM输出。

CVSS 6.3 · Medium EPSS 0.45% · P36

Affected Version Matrix 1

VendorProduct Version RangeStatus
klever-io klever-go < 1.7.17 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-46403

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Klever-Go KVM read-only execution can commit contract delete and upgrade side effects
Source: CVE Program / CVE List V5
Vulnerability Description
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: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
保护机制失效
Source: CVE Program / CVE List V5
Vulnerability Title
klever-io klever-go 处理逻辑错误漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
klever-go是 klever-io klever-go 1.7.17之前版本存在处理逻辑错误漏洞,该漏洞源于间接合约删除和升级路径未在只读模式下拒绝执行,破坏了隔离边界,可能导致合同通过只读执行调用删除钩子,产生状态变更的VM输出。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
klever-io klever-go < 1.7.17 -

II. Public POCs for CVE-2026-46403

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-46403

请登录查看更多情报信息。

Vendor Advisories for CVE-2026-46403 (1)

IV. Related Vulnerabilities

V. Comments for CVE-2026-46403

No comments yet


Leave a comment