NPM · JULY 2026 · EARLY WARNING

CentreStack Cryptographic Key Vulnerability: Early Warning

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.

CVE-2026-54363Severity: CRITICAL

CentreStack versions prior to 17.5 appear to contain a critical vulnerability involving a hardcoded cryptographic key, enabling unauthenticated attackers to forge encrypted tokens and potentially achieve remote code execution.

What happened

CentreStack before version 17.5 is under investigation for a hardcoded cryptographic key vulnerability. This issue 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.

The vulnerability has been assigned CVE-2026-54363 with a CVSS score of 9.1, indicating a critical severity level. To mitigate this vulnerability, it is recommended to upgrade CentreStack to version 17.5 or later. For more detailed information, primary sources should be consulted.

How 0Day mitigates this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If centrestack is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Join the 0Day waitlist →

← Back to all threats