Vulnerability in astrbot (CVE-2025-55449)
Summary
Vulnerability in astrbot (CVE-2025-55449). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.5.18 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-55449 has been found in astrbot.
Risk of unauthorized operations or information disclosure. CVSS score: 7.3/10.
What to do: upgrade astrbot to 3.5.18 or later.
If unsure, ask your IT team or search "astrbot CVE-2025-55449" on the vendor's site.
CVE-2025-55449 (astrbot) — CWE-321 / CVSS v3 7.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 3.5.18 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-321) exists in astrbot.
Check the vendor advisory for the affected versions of astrbot.
Severity: High (CVSS 7.3/10). Risk of unauthorized operations or information disclosure.
Update to 3.5.18.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'astrbot' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'astrbot' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
astrbotを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade astrbot to 3.5.18ステージング環境で 3.5.18 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- exploit cve@mitre.org
- package pypi.org
- web cve@mitre.org
- web github.com
- web github.com
- web github.com