{"id":"EUVD-2026-46390","enisaUuid":"1a7bcd3d-7c27-30e8-a9df-bd83cf1339e1","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.","datePublished":"Jul 21, 2026, 7:51:18 PM","dateUpdated":"Jul 22, 2026, 2:28:22 PM","baseScore":6.3,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N","references":"https://github.com/klever-io/klever-go/security/advisories/GHSA-jc6w-wmfc-fh33\nhttps://github.com/klever-io/klever-go/commit/333f6ec910906e227705fc5767dc897d8fbfc862\nhttps://github.com/klever-io/klever-go/commit/68b94a40824fac2d848a4ded6eb7c91ada6ce9ef\n","aliases":"CVE-2026-46403\nGHSA-jc6w-wmfc-fh33\n","assigner":"GitHub_M","epss":0.48,"enisaIdProduct":[{"id":"b467f8bd-2b14-3a65-b3ed-9de7d4a8f760","product":{"name":"klever-go","vendor":{"name":"klever-io"}},"product_version":"\u003c 1.7.17"}],"enisaIdVendor":[{"id":"e1c0a880-8f0f-3db1-af5c-0fd7594716dc","vendor":{"name":"klever-io"}}],"enisaIdVulnerability":[{"id":"56ae7871-7ea2-37af-ac2d-f2d57a82b314","vulnerability":{"id":"GHSA-jc6w-wmfc-fh33","description":"Klever-Go KVM read-only execution can commit contract delete and upgrade side effects","datePublished":"May 21, 2026, 4:53:32 PM","dateUpdated":"May 21, 2026, 4:53:32 PM","baseScore":0.0,"references":"https://github.com/klever-io/klever-go/security/advisories/GHSA-jc6w-wmfc-fh33\nhttps://github.com/klever-io/klever-go/commit/333f6ec910906e227705fc5767dc897d8fbfc862\nhttps://github.com/klever-io/klever-go/commit/68b94a40824fac2d848a4ded6eb7c91ada6ce9ef\nhttps://github.com/klever-io/klever-go\n","enisa_id":"EUVD-2026-46390\n","aliases":"CVE-2026-46403\nGHSA-jc6w-wmfc-fh33\n","epss":0.0,"dataProcessed":"Nov 1, 2026, 2:01:03 AM","vulnerabilityProduct":[],"vulnerabilityVendor":[]}},{"id":"56b2d538-2020-3a4c-8d01-e18c9cff09f1","vulnerability":{"id":"CVE-2026-46403","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.","datePublished":"Jul 21, 2026, 7:51:18 PM","dateUpdated":"Jul 22, 2026, 2:28:22 PM","status":"PUBLISHED","baseScore":6.3,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N","references":"https://github.com/klever-io/klever-go/security/advisories/GHSA-jc6w-wmfc-fh33\nhttps://github.com/klever-io/klever-go/commit/333f6ec910906e227705fc5767dc897d8fbfc862\nhttps://github.com/klever-io/klever-go/commit/68b94a40824fac2d848a4ded6eb7c91ada6ce9ef\n","enisa_id":"EUVD-2026-46390\n","assigner":"GitHub_M","epss":0.48,"dataProcessed":"Nov 5, 2026, 7:18:42 AM","vulnerabilityProduct":[{"id":"ef35c993-49e6-3134-8afd-16a6827f7942","product":{"name":"klever-go","vendor":{"name":"klever-io"}},"product_version":"\u003c 1.7.17"}],"vulnerabilityVendor":[{"id":"86587375-b734-300c-8ce0-24afb569d6b5","vendor":{"name":"klever-io"}}]}}],"enisaIdAdvisory":[]}