astrbot
Affected
- introduced
0, fixed3.5.18(ecosystem)
Fixed versions
3.5.18
Fix
- Fixed version
3.5.18pip install --upgrade astrbot==3.5.18
Advisory
Also known as: CVE-2025-55449, PYSEC-2026-285
AstrBot is vulnerable to RCE with hard-coded JWT signing keys
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.
Critical Basis: The source's own band: CRITICAL
0, fixed 3.5.18 (ecosystem)3.5.18
3.5.18pip install --upgrade astrbot==3.5.18Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0