Quick answers
- Is CVE-2026-8754 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-8754 being exploited in the wild.
- How severe is CVE-2026-8754?
- Medium severity, with a CVSS score of 6.3, published 17 May 2026.
- Which products and versions are affected?
- astrbot (PyPI) < 4.23.6, ECOSYSTEM:introduced=0,fixed=4.23.6.
- Is there a fix for CVE-2026-8754?
- Yes. astrbot (PyPI): upgrade to 4.23.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-8754 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-8754?
- Check whether you run astrbot (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- astrbot (PyPI): upgrade to 4.23.6 or later
pip install "astrbot>=4.23.6"
Technical details
A path traversal vulnerability exists in the `post_file` function within `astrbot/dashboard/routes/chat.py`. The application fails to sanitize the `filename` argument provided in multipart/form-data uploads, passing it directly to `os.path.join()` and subsequently `file.save()`. An authenticated attacker (or one using default credentials) can provide a filename containing traversal sequences (e.g., `../../`) to write files outside of the intended attachments directory. This can be leveraged to achieve remote code execution by overwriting application scripts or configuration files. The issue is fixed in version 4.23.6 by implementing proper filename sanitization and removing NUL bytes.
Affected products
- AstrBotDevs AstrBot < 4.23.6
Identifiers
- CVE-2026-8754
- GHSA-f63h-wc26-pmvc
- PYSEC-2026-2380
Timeline
- 2026-03-21: other: Vulnerability details shared via GitHub Gist
- 2026-05-17: disclosed: CVE-2026-8754 published
- 2026-05-17: advisory
- 2026-05-23: patched: GitHub Advisory reviewed and patch confirmed in 4.23.6