GitHub Advisoryadvisory · PyPI

GHSA-4m32-cjv7-f425 AstrBot is vulnerable to RCE with hard-coded JWT signing keys

CRITICAL Published 2025-11-14 Modified 2026-10-27 Official page ↗
Aliases
CVE-2025-55449
Ecosystem
PyPI
Packages
astrbot
Severity
Critical
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weaknesses
CWE-321, CWE-345, CWE-798
Reviewed
2025-11-14

Affected packages

• PyPI astrbot: < 3.5.18 → fixed in 3.5.18

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.

Related

Alias · CVE (1)

  • CVE-2025-55449 AstrBotDevs AstrBot 3.5.15 has Advanced_System_for_Text_Response_and_Bot_Operations_Tool as the hardcoded private key used to sign a JWT. vulnerability

Weakness · CWE (3)

  • CWE-321 Use of Hard-coded Cryptographic Key weakness
  • CWE-345 Insufficient Verification of Data Authenticity weakness
  • CWE-798 Use of Hard-coded Credentials weakness

References