AstrBot contains a directory traversal vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2025-57698: 0.83% estimated exploitation activity in the next 30 days; percentile 57.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

AstrBot Project v3.5.22 contains a directory traversal vulnerability. The handler function installpluginupload of the interface '/plugin/install-upload' parses the filename from the request body provided by the user, and directly uses the filename to assign to filepath without checking the validity of the filename. The variable filepath is then passed as a parameter to the function file.save, so that the file in the request body can be saved to any location in the file system through directory traversal.

Published by the source

7 Nov 2025, 18:30 UTC

Last modified by the source

7 Jul 2026, 17:57 UTC

Source last checked

26 Oct 2026, 13:35 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-xrj9-mw57-j34v

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-xrj9-mw57-j34v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-57698

Advisory: AstrBot contains a directory traversal vulnerability
IDs: CVE-2025-57698, GHSA-xrj9-mw57-j34v
Record: https://patchnext.com/advisories/cve-2025-57698 (revision 3, source checked 26 Oct 2026, 13:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI astrbot: affected <= 3.5.22

## Suggested inspection (read-only)
- `python -m pip show astrbot`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on astrbot.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-xrj9-mw57-j34v (OSV record GHSA-xrj9-mw57-j34v lists affected ranges: PyPI astrbot >=0 <=3.5.22)
- Verified: https://github.com/advisories/GHSA-xrj9-mw57-j34v (GitHub-reviewed advisory GHSA-xrj9-mw57-j34v lists affected ranges: PyPI astrbot >=0 <=3.5.22)

Commands are suggestions: review each one before running it.