Klever-Go KVM read-only execution can commit contract delete and upgrade side effects
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-46403
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 03:10 UTC · Revision 1
Source evidence
Klever-Go KVM read-only execution can commit contract delete and upgrade side effects
core-osv · Original sourcePublished 21 Jul 2026, 19:51 UTC
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.
osv:CVE-2026-46403
Complete source record
{
"id": "ba07d310c5fdea9fb5638944fb94c8710916fc5affbecdaf3af40254bfd527fb",
"url": "https://osv.dev/vulnerability/CVE-2026-46403",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Klever-Go KVM read-only execution can commit contract delete and upgrade side effects",
"summary": "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.",
"evidence": "osv:CVE-2026-46403",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2026-46403",
"aliases": [
"CVE-2026-46403",
"GHSA-jc6w-wmfc-fh33",
"GO-2026-5461"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/klever-io/klever-go",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "333f6ec910906e227705fc5767dc897d8fbfc862"
},
{
"fixed": "68b94a40824fac2d848a4ded6eb7c91ada6ce9ef"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"fixed": "1.7.17"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "333f6ec910906e227705fc5767dc897d8fbfc862"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "68b94a40824fac2d848a4ded6eb7c91ada6ce9ef"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v1.7.16",
"v1.7.15",
"v1.7.14"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-46403.json"
}
}
],
"modified": "2026-10-28T02:30:49.231234146Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/46xxx/CVE-2026-46403.json",
"https://github.com/klever-io/klever-go/security/advisories/GHSA-jc6w-wmfc-fh33",
"https://nvd.nist.gov/vuln/detail/CVE-2026-46403",
"https://github.com/klever-io/klever-go/commit/333f6ec910906e227705fc5767dc897d8fbfc862",
"https://github.com/klever-io/klever-go/commit/68b94a40824fac2d848a4ded6eb7c91ada6ce9ef"
],
"provider_metadata": {
"cwe_ids": [
"CWE-693"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/46xxx/CVE-2026-46403.json"
}
},
"related_cves": [
{
"value": "CVE-2026-46403",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 517641,
"published_at": "2026-07-21T19:51:18.745+00:00"
}