CVE-2026-54363

CentreStack < 17.5 Hardcoded Key Token Forgery RCE

Published Jul 30, 2026 CVSS 4.0 · 9.3 Critical EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

The vulnerability is a hardcoded cryptographic key flaw present in all versions of CentreStack prior to 17.5. It allows an attacker to forge encrypted authentication tokens by exploiting a static system number used as entropy in token encryption and decryption. With a forged x-glad-auth header, the attacker can invoke privileged API endpoints, such as acquiretenantbackuptoken, to obtain a domain administrator IdentityTicket. The chain of exploitation results in a fully uncontrolled code execution environment on the affected server.

Affected Systems

All installations of Gladinet CentreStack released before version 17.5 are impacted. The vulnerability exists across every deployment that has not applied the version 17.5 (or later) security update, affecting the entire product line regardless of deployment size or configuration.

Risk and Exploitability

The CVSS score of 9.3 reflects a high severity. Because the flaw requires no prior authentication, the attack is network‑based and can be performed from anywhere the API is exposed. The EPSS score is very low at < 1 %, and the vulnerability is not listed as a Known Exploited Vulnerability by CISA, but the impact and ease of exploitation warrant immediate attention. Exploitability hinges on the presence of the hardcoded key and the encryption routine; once an attacker obtains a forged token, they can move laterally within the CentreStack environment and gain administrator privileges.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the latest CentreStack release (17.5 or later) that removes the hard‑coded cryptographic key.
  • Re‑configure the system to enforce secure key handling and reject legacy authentication tokens if any remain.
  • Implement network‑level controls to block or monitor x‑glad‑auth headers from unauthenticated sources, ensuring only trusted clients can access privileged API endpoints.

Generated by OpenCVE AI on August 2, 2026 at 05:26 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:gladinet:centrestack:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Gladinet
Gladinet centrestack
Vendors & Products Gladinet
Gladinet centrestack
Type Values Removed Values Added
Description 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.
Title CentreStack < 17.5 Hardcoded Key Token Forgery RCE
Weaknesses CWE-321
References
Metrics cvssV3_1

{'score': 9.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N'}

cvssV4_0

{'score': 9.3, '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'}

Weaknesses
  • CWE-321

    Use of Hard-coded Cryptographic Key

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Aug 14, 2026, 4:50 PM
Reserved
Jun 12, 2026, 8:20 PM
Status
Deferred
Published
Jul 30, 2026, 1:16 PM
Modified
Oct 23, 2026, 10:10 PM