Advisory

PYSEC-2026-285

Also known as: CVE-2025-55449, GHSA-4m32-cjv7-f425

Summary

AstrBot is vulnerable to RCE with hard-coded JWT signing keys

Details

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.

Severity

Critical Basis: CVSS v3 score 9.8, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Dates

Published
2026-06-29 11:50 UTC
Modified
2026-07-01 20:22 UTC

Affected packages and fixes

astrbot

PyPI · All systems

Affected

  • introduced 0, fixed 3.5.18 (ecosystem)

Fixed versions

3.5.18

Fix

  • Fixed version 3.5.18
    pip install --upgrade astrbot==3.5.18

Fix 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

View this record on OSV.dev

Source

Source: PyPA Advisory Database · CC BY 4.0

Sources & licences