Quick answers
- Is CVE-2026-54363 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54363 being exploited in the wild.
- How severe is CVE-2026-54363?
- Critical severity, with a CVSS score of 9.1, published 30 July 2026.
- Which products and versions are affected?
- Gladinet CentreStack before 17.5.
- Is there a fix for CVE-2026-54363?
- A patch was published on 2026-07-30: Fixed in version 17.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54363 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-54363?
- Check whether you run Gladinet CentreStack at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
CentreStack versions prior to 17.5 utilize a hardcoded cryptographic key derived from a static 'SysNumber' value used as entropy for the AccessTicket.Encrypt() and AccessTicket.Decrypt() functions. Because this value is identical across all installations, an unauthenticated remote attacker can forge valid 'x-glad-auth' headers. By leveraging these forged headers, an attacker can access privileged API endpoints, such as 'acquiretenantbackuptoken', to obtain a domain administrator IdentityTicket. This sequence allows for a complete authentication bypass and subsequent remote code execution (RCE) on the affected server. The vulnerability is classified as CWE-321 (Use of Hard-coded Cryptographic Key).
Affected products
- Gladinet CentreStack before 17.5
Timeline
- 2026-07-30: advisory: Vulnerability disclosed by VulnCheck and NVD
- 2026-07-30: patched: Fixed in version 17.5