CVE-2026-54363

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-30. The CNA's CVSS baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.1Exploit: None knownExposed services: Not assessed

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

The CVE record's CNA (VulnCheck) lists Gladinet CentreStack versions before 17.5 as affected. No release containing a fix is confirmed on record.

CentreStack before 17.5 contains a hardcoded cryptographic key vulnerability that allows unauthenticated attackers to forge arbitrary encrypted tokens by exploiting a static SysNumber value used as entropy for AccessTicket.Encrypt() and AccessTicket.Decrypt() across all installations. Attackers can use the hardcoded key to craft valid x-glad-auth headers and call privileged API endpoints such as acquiretenantbackuptoken to obtain a domain administrator IdentityTicket, enabling a complete unauthenticated remote code execution chain.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.7%
EPSS %ILE
51st
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (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

July 30, 2026

Last Modified

August 14, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
No fix on record yet.
Web page

CentreStack < 17.5 Hardcoded Key Token Forgery RCE | Advisories | VulnCheck

https://www.vulncheck.com/advisories/centrestack-hardcoded-key-token-forgery-rce
Web page

CentreStack: Grow Your MSP with Your Branded File Solution

https://www.centrestack.com/

Vendor Advisories for CVE-2026-54363(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 89× 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 433 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 333 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-54363?
CVE-2026-54363 is a critical-severity vulnerability; its CVE record was published on July 30, 2026. CentreStack before 17.5 contains a hardcoded cryptographic key vulnerability that allows unauthenticated attackers to forge arbitrary encrypted tokens by exploiting a static SysNumber value used as entropy for AccessTicket.Encrypt() and AccessTicket.Decrypt() across all installations. Attackers can…
When was CVE-2026-54363 made public?
CVE-2026-54363 was made public on July 28, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 30, 2026. EchelonGraph's copy of the record carries a last-modified date of August 14, 2026; the record at its source may have been updated since.
Is CVE-2026-54363 actively exploited?
CVE-2026-54363 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54363?
CVE-2026-54363 has a CVSS base score of 9.1 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-54363?
No fix for CVE-2026-54363 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists Gladinet CentreStack versions before 17.5 as affected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-54363 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54363

Explore →

Is Your Infrastructure Affected by CVE-2026-54363?

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