{"answers":{"affected":"3 open source packages ship an affected version, including github.com/klever-io/klever-go.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46403 exists.","fix":"Upgrade github.com/klever-io/klever-go to 1.7.17 or later.","what":"CVE-2026-46403 is a medium-severity missing authorization vulnerability in klever-io klever-go, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-46403 and fix it if it is affected.\n\nWhat it is: CVE-2026-46403 is a medium-severity missing authorization vulnerability in klever-io klever-go, published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46403 exists.\n\nAffected packages and fixed versions:\n- github.com/klever-io/klever-go (Go): affected all versions; fixed in 1.7.17\n- github.com/klever-io/klever-go (Go): affected all versions; fixed in 1.7.17\n- github.com/klever-io/klever-go (Go): affected all versions; fixed in 1.7.17\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-46403/ (Markdown: https://insights.sbomify.com/CVE-2026-46403/index.md)","id":"CVE-2026-46403","markdown":"https://insights.sbomify.com/CVE-2026-46403/index.md","name":"CVE-2026-46403","record":{"aliases":["GHSA-jc6w-wmfc-fh33","GO-2026-5461"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Klever blockchain library","requires_auth":"low_privilege","summary":"Attackers can trigger contract deletion and upgrades via read-only execution paths, bypassing intended state isolation in the Klever-Go blockchain library.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-693","name":"Protection Mechanism Failure"}],"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Klever-Go KVM read-only execution can commit contract delete and upgrade side effects","id":"CVE-2026-46403","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"BigBlueButton: Presentation URL Security Hardening","id":"CVE-2026-46404"},"packages":[{"ecosystem":"Go","fixed":["1.7.17"],"introduced":["0"],"last_affected":[],"package":"github.com/klever-io/klever-go","purl":null,"source":"GHSA-jc6w-wmfc-fh33"},{"ecosystem":"Go","fixed":["1.7.17"],"introduced":["0"],"last_affected":[],"package":"github.com/klever-io/klever-go","purl":"pkg:golang/github.com/klever-io/klever-go","source":"GHSA-jc6w-wmfc-fh33"},{"ecosystem":"Go","fixed":["1.7.17"],"introduced":["0"],"last_affected":[],"package":"github.com/klever-io/klever-go","purl":"pkg:golang/github.com/klever-io/klever-go","source":"GO-2026-5461"}],"prev":{"headline":"Path traversal in UFO","id":"CVE-2026-46402"},"products":["klever-go"],"published":"2026-07-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-22","vendors":["klever-io"]},"summary":"Attackers can trigger contract deletion and upgrades via read-only execution paths, bypassing intended state isolation in the Klever-Go blockchain library.","url":"https://insights.sbomify.com/CVE-2026-46403/"}