CVE-2026-55763

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
8.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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: 8.7Exploit: 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.19, processPercentageRoyaltiesTransfer in core/kapp/accounts/accounts.go calls SubFromBalance after the split loop and after the royaltiesToPay <= 0 early return. computeSplitRoyalties rejects only when splitToPay > royaltiesToPay, so a valid PercentTransferPercentage = 10000 split consumes exactly 100 percent of the royalty pool, sets royaltiesToPay to zero, and returns before the source account is debited. The split recipient receives the full royaltyAmount while the sender pays nothing and the supply counter is not updated, allowing unbounded off-the-books inflation of the transferred KDA. A KDA owner must configure a TransferPercentage royalty with a 100 percent split, after which any holder's transfer of the asset triggers the mint; the sibling processFixedRoyaltiesTransfer path is not affected because it debits the source before distribution. This issue is fixed in version 1.7.19.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
70
EG Risk 70/100

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 (value × EchelonGraph’s weight)
Severity87% × 45%
The EG Score, 8.7 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

August 28, 2026

Last Modified

September 9, 2026

Advisory Details (3)

Auto-updated Aug 28, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Percentage-transfer royalty skips the source debit at exactly-100% splits · Advisory · klever-io/klever-go · GitHub

https://github.com/klever-io/klever-go/security/advisories/GHSA-v358-wf77-39xv
GitHub release Patch Available

v1.7.19 - Marketplace & SFT Mint Security Release

Patch available: klever-io/klever-go v1.7.19

https://github.com/klever-io/klever-go/releases/tag/v1.7.19
GitHub commit Patch Available

commit 8bcc600b0ac8 (klever-io/klever-go)

Patch available: klever-io/klever-go v1.7.19 (contains commit 8bcc600b0ac8)

https://github.com/klever-io/klever-go/commit/8bcc600b0ac88070740c63c7ce1c8a968dd85251

Vendor Advisories for CVE-2026-55763(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 rangeFix by version rangeDependents
github.com/klever-io/klever-go—
  • every version up to 1.7.19-rc4: fixed in 1.7.19-rc4
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 54× 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.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-12 15:55 UTCEG score recompute
  4. 2026-10-11 19:38 UTCEG score recompute
  5. 2026-10-11 16:53 UTCEG score recompute
  6. 2026-10-11 14:16 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  9. 2026-10-10 00:48 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-09 02:37 UTCEG score recompute
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-08 00:48 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  15. 2026-10-06 20:27 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  17. 2026-10-06 07:27 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  19. 2026-10-05 03:40 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  21. 2026-10-04 02:15 UTCEG score recompute
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  23. 2026-10-02 22:19 UTCEG score recompute
  24. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  25. 2026-10-01 21:04 UTCEG score recompute
Show 59 more
  1. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-09-30 19:48 UTCEG score recompute
  3. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  4. 2026-09-30 03:49 UTCEG score recompute
  5. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  6. 2026-09-28 23:29 UTCEG score recompute
  7. 2026-09-27 22:14 UTCEG score recompute
  8. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  9. 2026-09-26 20:55 UTCEG score recompute
  10. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-09-26 08:03 UTCEG score recompute
  12. 2026-09-24 18:42 UTCEG score recompute
  13. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-09-24 05:22 UTCEG score recompute
  15. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  16. 2026-09-22 15:29 UTCEG score recompute
  17. 2026-09-22 02:50 UTCEG score recompute
  18. 2026-09-21 01:35 UTCEG score recompute
  19. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  20. 2026-09-19 23:23 UTCEG score recompute
  21. 2026-09-18 22:05 UTCEG score recompute
  22. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  23. 2026-09-17 20:50 UTCEG score recompute
  24. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  25. 2026-09-16 18:58 UTCEG score recompute
  26. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  27. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  28. 2026-09-15 03:30 UTCEG score recompute
  29. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  30. 2026-09-14 02:14 UTCEG score recompute
  31. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  32. 2026-09-13 00:59 UTCEG score recompute
  33. 2026-09-11 23:43 UTCEG score recompute
  34. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  35. 2026-09-11 11:05 UTCEG score recompute
  36. 2026-09-10 09:49 UTCEG score recompute
  37. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  38. 2026-09-09 00:26 UTCEG score recompute
  39. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  40. 2026-09-07 02:10 UTCEG score recompute
  41. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  42. 2026-09-06 00:47 UTCEG score recompute
  43. 2026-09-04 23:30 UTCEG score recompute
  44. 2026-09-04 10:49 UTCEG score recompute
  45. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  46. 2026-09-02 20:23 UTCEG score recompute
  47. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  48. 2026-09-01 16:46 UTCEG score recompute
  49. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  50. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  51. 2026-08-31 15:30 UTCEG score recompute
  52. 2026-08-31 14:27 UTCEG score recompute
  53. 2026-08-31 01:08 UTCEG score recompute
  54. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  55. 2026-08-30 12:30 UTCEG score recompute
  56. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  57. 2026-08-28 22:35 UTCEG score recomputeFirst assessed: 8.7 HIGH
  58. 2026-08-28 22:34 UTCNVD updateCVSS v3 → 8.7 · CVSS v4 → 8.7
  59. 2026-08-28 21:11 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-55763?
CVE-2026-55763 is a high-severity vulnerability; its CVE record was published on August 28, 2026. Klever-Go is the Go implementation of the Klever blockchain protocol. Prior to 1.7.19, processPercentageRoyaltiesTransfer in core/kapp/accounts/accounts.go calls SubFromBalance after the split loop and after the royaltiesToPay <= 0 early return. computeSplitRoyalties rejects only when splitToPay >…
When was the CVE record for CVE-2026-55763 published?
The CVE record for CVE-2026-55763 was published on August 28, 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 September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-55763 actively exploited?
CVE-2026-55763 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-55763?
CVE-2026-55763 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55763?
A fix for CVE-2026-55763 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55763 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-55763

Explore →

Is Your Infrastructure Affected by CVE-2026-55763?

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

Book a Demo →Browse All CVEs