CVE-2025-48957

Reproduce

Follow these steps to set up a test environment for reproducing the vulnerability:

1. Install dependencies and clone the repository:

   pip install uv
   git clone https://github.com/AstrBotDevs/AstrBot && cd AstrBot
   uv run main.py
   

2. Alternatively, deploy the program via pip:

   mkdir astrbot && cd astrbot
   uvx astrbot init
   uvx astrbot run
   

3. In another terminal, run the following command to exploit the vulnerability:

   curl -L http://0.0.0.0:6185/api/chat/get_file?filename=../../../data/cmd_config.json
   

This request will read the cmd_config.json config file, leading to the leakage of sensitive data such as LLM API keys, usernames, and password hashes (MD5).

Workarounds

Users can edit the cmd_config.json file to disable the dashboard feature as a temporary workaround. However, it is strongly recommended to upgrade to version v3.5.13 or later as soon as possible to fully resolve this issue.

References

• Pull Request #1676
• Issue #1675

This vulnerability may lead to:

• Information disclosure, such as API keys for LLM providers, account passwords, and other sensitive data.

CVE-2025-48957 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.5.13); upgrading removes the vulnerable code path.

Kodem intelligence

The vulnerability has been addressed in Pull Request #1676 and is included in versions >= v3.5.13. All users are strongly encouraged to upgrade to v3.5.13 or later.

1. What is CVE-2025-48957? CVE-2025-48957 is a high-severity security vulnerability in astrbot (pip), affecting versions >= 3.4.4, <= 3.5.12. It is fixed in 3.5.13.
2. How severe is CVE-2025-48957? CVE-2025-48957 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of astrbot are affected by CVE-2025-48957? astrbot (pip) versions >= 3.4.4, <= 3.5.12 is affected.
4. Is there a fix for CVE-2025-48957? Yes. CVE-2025-48957 is fixed in 3.5.13. Upgrade to this version or later.
5. Is CVE-2025-48957 exploitable, and should I be worried? Whether CVE-2025-48957 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-48957 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-48957? Upgrade astrbot to 3.5.13 or later.