Skip to main content
VulnerabilityPublished Updated

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

Affects astrbotSource GCVE Database

0
Authoritative record:CVE-2025-55449· High 7.3

Not known to be exploited · CVSS 7.3 High : upgrade to 3.5.18 soon.

Data as of 27 Oct 2026, 17:59 UTC

CVSS 3.1 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.5.18
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade astrbot to 3.5.18.

Affected software

ProductAffectedFixed in
PyPIastrbotAffected
  • <3.5.18
Fixed in
  • 3.5.18

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade AstrBot to version 3.5.18 or later, which contains the official fix for this vulnerability. Instances running earlier versions remain vulnerable and should be updated immediately. No additional mitigations are indicated by the vendor advisory.

Description

AstrBot versions prior to 3.5.18 contain a critical vulnerability due to a hard-coded JWT signing key. This flaw allows attackers to bypass authentication and install malicious Python plugins, resulting in arbitrary command execution on the host. The vulnerability was patched in version 3.5.18 on the same day it was reported (2025-06-21). Public disclosure occurred later on 2025-11-14, by which time most instances had been updated.

References

Community reviews

Loading reviews…