AstrBot is vulnerable to RCE with hard-coded JWT signing keys
🔗 CVE IDs covered (1)
📋 Description
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.
🎯 Affected products1
- pip/astrbot:< 3.5.18
🔗 References (8)
- https://github.com/AstrBotDevs/AstrBot/security/advisories/GHSA-4m32-cjv7-f425
- https://github.com/AstrBotDevs/AstrBot/commit/d03e9fb90a0921a1bd10cf480bdacc9aaa246472
- https://github.com/AstrBotDevs/AstrBot/releases/tag/v3.5.18
- https://github.com/Marven11/CVE-2025-55449-AstrBot-RCE
- https://nvd.nist.gov/vuln/detail/CVE-2025-55449
- https://github.com/pypa/advisory-database/tree/main/vulns/astrbot/PYSEC-2026-285.yaml
- https://pypi.org/project/astrbot
- https://github.com/advisories/GHSA-4m32-cjv7-f425