Path Traversal in AstrBot (CVE-2026-8754)
Summary
Path traversal in AstrBot (CVE-2026-8754). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 4.23.6 or later.
Original description
The description as published by the source.
A vulnerability was detected in AstrBotDevs AstrBot up to 4.23.5. Impacted is the function post_file of the file astrbot/dashboard/routes/chat.py of the component File Upload Handler. The manipulation of the argument filename results in path traversal. It is possible to launch the attack remotely. The exploit is now public and may be used. Upgrading to version 4.23.6 is recommended to address this issue. The patch is identified as aaec41e5054569ceaa1113593a34da7568e2d211. You should upgrade the affected component.
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-2026-8754 has been found in AstrBot.
Risk of unauthorized operations or information disclosure. CVSS score: 6.3/10.
What to do: upgrade AstrBot to 4.23.6 or later.
If unsure, ask your IT team or search "AstrBot CVE-2026-8754" on the vendor's site.
CVE-2026-8754 (AstrBot) — CWE-22 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.23.6 — 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.
Path traversal (CWE-22) exists in AstrBot.
Check the vendor advisory for the affected versions of AstrBot.
Severity: Medium (CVSS 6.3/10). Risk of unauthorized operations or information disclosure.
Update to 4.23.6.
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 4.23.6ステージング環境で 4.23.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory vuldb.com
- advisory vuldb.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- report gist.github.com
- report vuldb.com
- web github.com
- web github.com