Security Digest · Vulnerability record

CVE-2025-55449: AstrBot is vulnerable to RCE with hard-coded JWT signing keys

AstrBotDevs AstrBot 3.5.15 has AdvancedSystemforTextResponseandBotOperationsTool as the hardcoded private key used to sign a JWT.

CVSS 7.3 High EPSS 0.3% · p19

Should you act?

Normal patch cycle

No exploitation signal; fix it in your next routine update if you are affected. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.

  • No confirmed exploitation. It is not in CISA’s KEV catalog and CISA’s SSVC assessment records no known exploitation. That can change quickly after a public write-up; re-check if you are affected.
  • EPSS 0.3%, percentile 19: FIRST’s model estimates a 0.3% chance of exploitation activity in the next 30 days, higher than 19% of all scored CVEs (low). EPSS is a probability, not a verdict.
  • Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
  • Only applies if your dependency tree includes astrbot (PyPI) < 3.5.18, fixed in 3.5.18. Check your lockfile, including transitive dependencies.

What it is

AstrBotDevs AstrBot 3.5.15 has AdvancedSystemforTextResponseandBotOperationsTool as the hardcoded private key used to sign a JWT.

From the GitHub advisory

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.

Weakness type: CWE-321, CWE-345, CWE-798.

Product: astrbot (PyPI) · Assigned by: mitre · Published: 2026-05-08

Affected and fixed versions

EcosystemPackageVulnerableFirst fixed
PyPIastrbot< 3.5.183.5.18
VendorProductAffected versions (per CVE record)
n/an/asee vendor advisory

Severity scores

Scored byCVSSScoreVector
CISA-ADP3.17.3 HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
GitHub3.19.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • Attack vector: network (remotely reachable)
  • Attack complexity: low
  • Privileges required: none (no login)
  • User interaction: none
  • Scope: unchanged

CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.

Exploitation and urgency

  • CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
  • CISA SSVC assessment: exploitation none, automatable yes, technical impact partial.
  • FIRST EPSS (model of 2026-10-21): 0.28% probability of exploitation activity in the next 30 days; percentile 19.

Timeline

  • — GitHub-reviewed advisory GHSA-4m32-cjv7-f425 published (critical)
  • — CVE record last updated
  • — CVE record published by mitre

Sources and references

Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.

Vulnerability records

  1. GitHub Advisory GHSA-4m32-cjv7-f425 github.com
  2. CVE.org record CVE-2025-55449 cve.org
  3. NVD entry CVE-2025-55449 nvd.nist.gov

Other references from the CVE record and advisory

  1. github.com github.com
  2. github.com github.com
  3. github.com github.com
  4. github.com github.com
  5. github.com github.com

Critical PyPI advisories · Today’s Security Digest