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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2025-55449: 0.28% estimated exploitation activity in the next 30 days; percentile 20.62 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

14 Nov 2025, 21:52 UTC

Last modified by the source

27 Oct 2026, 15:30 UTC

Source last checked

28 Oct 2026, 06:10 UTC

1. Revision 5 · amended · 28 Oct 2026

   Amended from osv record GHSA-4m32-cjv7-f425

2. Revision 4 · amended · 27 Oct 2026

   Amended from ghsa record GHSA-4m32-cjv7-f425

3. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-4m32-cjv7-f425

4. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-4m32-cjv7-f425

5. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-4m32-cjv7-f425

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-55449

Advisory: AstrBot is vulnerable to RCE with hard-coded JWT signing keys
IDs: CVE-2025-55449, GHSA-4m32-cjv7-f425
Record: https://patchnext.com/advisories/cve-2025-55449 (revision 5, source checked 28 Oct 2026, 06:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: astrbot 3.5.18. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI astrbot: affected < 3.5.18; fixed in 3.5.18

## Suggested inspection (read-only)
- `python -m pip show astrbot`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on astrbot.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4m32-cjv7-f425 (GitHub-reviewed advisory GHSA-4m32-cjv7-f425 lists affected ranges: PyPI astrbot >=0 <3.5.18)
- Verified: https://osv.dev/vulnerability/GHSA-4m32-cjv7-f425 (OSV record GHSA-4m32-cjv7-f425 lists affected ranges: PyPI astrbot >=0 <3.5.18 (fixed))

Commands are suggestions: review each one before running it.