CVE-2026-46403

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
6.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.3
EG Score
6.3(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity63% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

May 21, 2026

Last Modified

July 23, 2026

Advisory Details (3)

Auto-updated Jul 21, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github.
github Patch Available🟡 PoC Available

Klever-Go KVM read-only execution can commit contract delete and upgrade side effects · Advisory · klever-io/klever-go · GitHub

https://github.com/klever-io/klever-go/security/advisories/GHSA-jc6w-wmfc-fh33
github_commit Patch Available

commit 68b94a40824f (klever-io/klever-go)

Patch available: klever-io/klever-go v1.7.17 (contains commit 68b94a40824f)

https://github.com/klever-io/klever-go/commit/68b94a40824fac2d848a4ded6eb7c91ada6ce9ef
github_commit Patch Available

commit 333f6ec91090 (klever-io/klever-go)

Patch available: klever-io/klever-go v1.7.17 (contains commit 333f6ec91090)

https://github.com/klever-io/klever-go/commit/333f6ec910906e227705fc5767dc897d8fbfc862

Vendor Advisories for CVE-2026-46403(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/klever-io/klever-go1.7.17

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 47× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-21 21:46 UTCEG score recompute
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 18:47 UTCEG score recompute
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-17 09:48 UTCEG score recompute
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 03:24 UTCEG score recompute
  12. 2026-08-16 02:14 UTCEPSS rescore
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 01:57 UTCEG score recompute
  15. 2026-08-13 22:00 UTCEPSS rescore
  16. 2026-08-12 20:14 UTCEG score recompute
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-11 22:26 UTCEG score recompute
  19. 2026-08-11 00:31 UTCEG score recompute
  20. 2026-08-11 00:00 UTCEPSS rescore
  21. 2026-08-09 23:15 UTCEG score recompute
  22. 2026-08-09 13:46 UTCEPSS rescore
  23. 2026-08-09 01:28 UTCEG score recompute
  24. 2026-08-08 16:37 UTCEPSS rescore
  25. 2026-08-07 16:49 UTCEG score recompute
Show 29 more
  1. 2026-08-06 19:01 UTCEG score recompute
  2. 2026-08-06 13:47 UTCEPSS rescore
  3. 2026-08-05 21:13 UTCEG score recompute
  4. 2026-08-05 19:17 UTCEPSS rescore
  5. 2026-08-04 15:10 UTCEPSS rescore
  6. 2026-08-04 10:39 UTCEPSS rescore
  7. 2026-08-03 16:51 UTCEG score recompute
  8. 2026-08-03 10:36 UTCEPSS rescore
  9. 2026-08-02 15:19 UTCEG score recompute
  10. 2026-08-02 02:27 UTCEPSS rescore
  11. 2026-08-01 17:30 UTCEG score recompute
  12. 2026-08-01 04:16 UTCEPSS rescore
  13. 2026-07-30 16:28 UTCEPSS rescore
  14. 2026-07-30 01:30 UTCEPSS rescore
  15. 2026-07-29 17:54 UTCEG score recompute
  16. 2026-07-28 15:36 UTCEPSS rescore
  17. 2026-07-27 14:13 UTCEPSS rescore
  18. 2026-07-26 14:54 UTCEPSS rescore
  19. 2026-07-26 14:54 UTCEPSS rescore
  20. 2026-07-26 08:10 UTCEG score recompute
  21. 2026-07-25 14:18 UTCEPSS rescore
  22. 2026-07-24 14:17 UTCEPSS rescore
  23. 2026-07-23 14:18 UTCEPSS rescore
  24. 2026-07-23 03:17 UTCEG score recompute
  25. 2026-07-22 14:08 UTCEPSS rescore
  26. 2026-06-14 23:18 UTCEPSS rescore
  27. 2026-06-13 23:00 UTCEPSS rescore
  28. 2026-06-12 23:12 UTCEPSS rescore
  29. 2026-05-24 06:12 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-46403?
CVE-2026-46403 is a medium vulnerability published on May 21, 2026. 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…
When was CVE-2026-46403 disclosed?
CVE-2026-46403 was first published in the National Vulnerability Database on May 21, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46403 actively exploited?
CVE-2026-46403 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 72.5% of all scored CVEs.
What is the CVSS score of CVE-2026-46403?
CVE-2026-46403 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2026-46403?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46403, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46403

Explore →

Is Your Infrastructure Affected by CVE-2026-46403?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.