Quick answers
- Is CVE-2025-55449 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-55449 being exploited in the wild.
- How severe is CVE-2025-55449?
- Critical severity, with a CVSS score of 9.8, published 8 May 2026.
- Which products and versions are affected?
- astrbot (PyPI) < 3.5.18, ECOSYSTEM:introduced=0,fixed=3.5.18.
- Is there a fix for CVE-2025-55449?
- Yes. astrbot (PyPI): upgrade to 3.5.18 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-55449 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2025-55449?
- Check whether you run astrbot (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- astrbot (PyPI): upgrade to 3.5.18 or later
pip install "astrbot>=3.5.18"
Technical details
AstrBot (up to version 3.5.17) utilizes a hardcoded secret key ('Advanced_System_for_Text_Response_and_Bot_Operations_Tool') for signing and validating JSON Web Tokens (JWT). Because this key is static and publicly available in the source code, an unauthenticated remote attacker can forge valid JWTs to impersonate administrative users. This authentication bypass can be leveraged to perform administrative actions, such as uploading malicious plugins, which leads to Remote Code Execution (RCE) on the underlying system. The vulnerability is classified as CWE-321 (Use of Hard-coded Cryptographic Key).
Affected products
- AstrBotDevs AstrBot <= 3.5.17
Identifiers
- CVE-2025-55449
- GHSA-4m32-cjv7-f425
- PYSEC-2026-285
Timeline
- 2026-05-08: advisory: Initial disclosure of CVE-2025-55449