CVE-2025-55449: Critical severity AstrBot AstrBot vulnerability
Summary AstrBot uses a hard-coded JWT signing key, allowing attackers to execute arbitrary commands by installing a malicious plugin.
Details
AstrBot uses a hard-coded JWT signing key, which allows attackers to bypass the authentication mechanism. Once bypassed, the attacker can install a Python plugin that will be imported here, enabling arbitrary command execution on the target host.
Impact
All publicly accessible AstrBot instances are vulnerable.
For more information, please see: CVE-2025-55449-AstrBot-RCE
Patch
This vulnerability was first reported on 2025-06-21 and was patched on the same day (2025-06-21).
The vulnerability was publicly disclosed on 2025-11-14. Prior to public disclosure, monitoring from AstrBot Cloud indicated that fewer than 2% of deployed instances were still running the affected version. Therefore, this disclosure is not expected to have a significant impact on existing active instances.
Other sources
AstrBotDevs AstrBot 3.5.15 has AdvancedSystemforTextResponseandBotOperationsTool as the hardcoded private key used to sign a JWT.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-55449?
CVE-2025-55449 is classified as a critical vulnerability due to the potential for attackers to execute arbitrary commands.
How do I fix CVE-2025-55449?
To fix CVE-2025-55449, upgrade AstrBot to version 3.5.18 or later.
What causes CVE-2025-55449?
CVE-2025-55449 is caused by the use of a hard-coded JWT signing key in the AstrBot application.
What type of attacks can be executed due to CVE-2025-55449?
Attackers can execute arbitrary commands by installing a malicious plugin due to CVE-2025-55449.
Which versions of AstrBot are affected by CVE-2025-55449?
Versions of AstrBot prior to 3.5.18 are affected by CVE-2025-55449.