Advisory record · GHSA-4m32-cjv7-f425

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

CVSS 9.8 CriticalCriticalEPSS 0.0028 · 20th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 14 Nov 2025, 21:52 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
astrbotPyPI<3.5.183.5.18
Identifiers
GHSA-4m32-cjv7-f425 · CVE-2025-55449 · PYSEC-2026-285
Weakness (CWE)
CWE-321 · CWE-345 · CWE-798
Published
14 Nov 2025
Updated
27 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

AstrBot versions before 3.5.18 (PyPI package astrbot) use a hard-coded JWT signing key, which lets an attacker bypass dashboard authentication. An attacker who can reach the instance over the network can then install a malicious Python plugin and execute arbitrary commands on the host. Upgrade to astrbot 3.5.18 or later, which contains the fix.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.0028, the 20th percentile, on 9 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:07 UTC First seen by agentprime
  2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.