CVE-2026-46403

MEDIUMPre-NVD 6.36.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.3 from GitHub Security Advisory (severity: MODERATE) published 2026-05-21. A secondary CVSS source baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-46390 (ENISA EUVD) · GHSA-jc6w-wmfc-fh33 (GitHub Security Advisories)Source: ENISA EUVD

6.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.3MEDIUMmedium confidence
EG Risk
44
EG Risk 44/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity63% × 45%
Impact severity (EG Severity): CVSS 6.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.

EG Severity
6.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 21, 2026

Last Modified

October 24, 2026

Advisory Details (3)

Auto-updated Jul 21, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

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.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/klever-io/klever-go @ 1.7.17 (fixes < 1.7.17)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/klever-io/klever-go—
  • every version up to 1.7.17: fixed in 1.7.17
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 127 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 27 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-11-01 07:48 UTCGHSA enrichmentGHSA-jc6w-wmfc-fh33 · GitHub severity MODERATE · GitHub CVSS 6.3
  4. 2026-11-01 07:48 UTCEG score recompute
  5. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-25 14:25 UTCEG score recompute
  13. 2026-10-24 19:27 UTCEG score recompute
  14. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  16. 2026-10-22 23:24 UTCEG score recompute
  17. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  18. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  19. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  20. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  21. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  22. 2026-10-18 03:37 UTCEG score recompute
  23. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  24. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  25. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 37th percentile
Show 75 more
  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  2. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  3. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  4. 2026-10-12 16:02 UTCEG score recompute
  5. 2026-10-11 19:45 UTCEG score recompute
  6. 2026-10-11 17:00 UTCEG score recompute
  7. 2026-10-11 14:25 UTCEG score recompute
  8. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  12. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  13. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  14. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  15. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  16. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  19. 2026-09-30 02:40 UTCOSV refresh
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  21. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  22. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  23. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  24. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  25. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  26. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 38th percentile
  27. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  28. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  29. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  30. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  31. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  32. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  33. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  34. 2026-09-11 04:23 UTCOSV refresh
  35. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  36. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  37. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  38. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  39. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  40. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  41. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  42. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  43. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  44. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  45. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  46. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  47. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  48. 2026-08-23 16:49 UTCEG score recompute
  49. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  50. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  51. 2026-08-21 21:46 UTCEG score recompute
  52. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  53. 2026-08-20 18:47 UTCEG score recompute
  54. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  55. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  56. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  57. 2026-08-17 09:48 UTCEG score recompute
  58. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  59. 2026-08-16 03:24 UTCEG score recompute
  60. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  61. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  62. 2026-08-14 01:57 UTCEG score recompute
  63. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  64. 2026-08-12 20:14 UTCEG score recompute
  65. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  66. 2026-08-11 22:26 UTCEG score recompute
  67. 2026-08-11 00:31 UTCEG score recompute
  68. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  69. 2026-08-09 23:15 UTCEG score recompute
  70. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  71. 2026-08-09 01:28 UTCEG score recompute
  72. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  73. 2026-08-07 16:49 UTCEG score recompute
  74. 2026-08-06 19:01 UTCEG score recompute
  75. 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.3% · 26th percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-46403?
CVE-2026-46403 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-46403 published?
The CVE record for CVE-2026-46403 was published on May 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-46403 actively exploited?
CVE-2026-46403 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-46403?
CVE-2026-46403 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-46403?
A fix for CVE-2026-46403 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-46403 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs