CVE-2026-54363
Hardcoded crypto key in CentreStack allows forging auth tokens, enabling unauthenticated RCE.
Is CVE-2026-54363 being exploited?
Not confirmed. CVE-2026-54363 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-54363?
CVE-2026-54363 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-54363?
Yes. A fix has been recorded for CVE-2026-54363. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-54363 affect?
CVE-2026-54363 affects CentreStack < 17.5, AccessTicket.Encrypt/Decrypt using static SysNumber. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-54363?
Upgrade to CentreStack 17.5+ or apply vendor patch; rotate keys, revoke tokens, audit access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attackers can forge x-glad-auth tokens, call privileged APIs to obtain a domain-admin IdentityTicket and achieve remote code execution.
Immediate action required
- affected< 17.5
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.