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

> Unauthenticated attackers can forge tokens using a hardcoded key to gain domain administrator privileges and execute remote code on CentreStack servers.

- **Severity:** Critical 9.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2026
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-vmg2-rwj3-8rq2

## What is CVE-2026-54363?

CVE-2026-54363 is a critical vulnerability in Gladinet CentreStack, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2026-54363?


## How do I fix CVE-2026-54363?

No fix has been published for CVE-2026-54363 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-54363 being exploited?

There is no known exploitation of CVE-2026-54363 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54363 and fix it if it is affected.

What it is: CVE-2026-54363 is a critical vulnerability in Gladinet CentreStack, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54363 in the wild and no public exploit code.

Affected product: Gladinet CentreStack. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54363/ (Markdown: https://insights.sbomify.com/CVE-2026-54363/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54363
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54363
- OSV: https://osv.dev/vulnerability/CVE-2026-54363

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54363/
Summaries are generated and may contain mistakes; the official description above is the record.