Security readout for executives and security teams
Plain-English summary
CentreStack versions earlier than 17.5 use the same embedded cryptographic value across installations. An unauthenticated internet attacker could forge trusted tokens, gain domain-administrator authority, and ultimately run code remotely. A successful compromise could expose or alter data and provide control of the CentreStack server.
Executive priority
Act immediately. Inventory exposed CentreStack systems, restrict access, investigate for compromise, and move affected installations to a confirmed fixed release. The lack of confirmed active exploitation reduces certainty about current attacks, not the potential business impact.
Technical view
The static SysNumber value supplies entropy to AccessTicket encryption and decryption, enabling forged x-glad-auth tokens. Those tokens can reach privileged APIs, including acquiretenantbackuptoken, and obtain a domain-administrator IdentityTicket. The reported chain requires no credentials or user interaction and can culminate in remote code execution.
Likely exposure
CentreStack deployments earlier than 17.5 are affected. Risk is greatest where the service and relevant API endpoints are reachable from untrusted networks. The supplied affected-version metadata is inconsistent, listing version “0,” so inventories should rely on the advisory’s explicit “before 17.5” boundary and confirm it with Gladinet.
Exploitation context
The supplied sources describe a complete, low-complexity, unauthenticated attack chain. However, the CVE is not listed as KEV, and the bundle provides no evidence of active exploitation. Treat exploitation as technically credible but not confirmed in the wild from these sources.
Researcher notes
CWE-321 applies because cryptographic key material is hardcoded and shared across installations. CVSS 4.0 is 9.3, with network reachability, low complexity, no privileges, and no interaction. The bundle reports high confidentiality and integrity impact but no direct availability impact. Independent reproduction details and telemetry indicators are not provided.
Mitigation direction
- Identify and prioritize every CentreStack deployment earlier than version 17.5.
- Upgrade to CentreStack 17.5 or later after confirming current Gladinet guidance.
- Restrict CentreStack and privileged API access to trusted networks until remediation is complete.
- Review potentially exposed systems for compromise before returning them to normal service.
Validation and detection
- Confirm each deployed CentreStack version and record whether it is earlier than 17.5.
- Determine whether CentreStack or its APIs are reachable from untrusted networks.
- Review logs for unexpected x-glad-auth use and calls to acquiretenantbackuptoken.
- Investigate unexplained domain-administrator IdentityTicket issuance or subsequent privileged activity.
- After upgrading, verify all instances report version 17.5 or later.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-321: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-54363 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Product HomepageCVE reference, VulnCheck · product
- https://www.vulncheck.com/advisories/centrestack-hardcoded-key-token-forgery-rceCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Hard-coded Cryptographic Key
Use of Hard-coded Cryptographic Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.