CVE-2025-57697 json
AstrBot has an arbitrary file read vulnerability in function _encode_image_bs64
published 2025-11-07 12 mo ago modified 2026-11-05 3 d ago also GHSA-vm2f-46xc-5jc3 , PYSEC-2026-1197 , EUVD-2025-38261
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
AstrBot Project v3.5.22 has an arbitrary file read vulnerability in function _encode_image_bs64. Since the _encode_image_bs64 function defined in entities.py opens the image specified by the user in the request body and returns the image content as a base64-encoded string without checking the legitimacy of the image path, attackers can construct a series of malicious URLs to read any specified file, resulting in sensitive data leakage.
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 11 mo ago
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/DYX217/vulnerability-explore/blob/main/1/README.md referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | astrbot | <=3.5.22 |
no fix listed |
Classification
References
-
github.com
/DYX217/vulnerability-explore/blob/main/1/README.md
web, exploit, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-57697
advisory
-
github.com
/AstrBotDevs/AstrBot
package
-
pypi.org
/project/astrbot
package
-
github.com
/advisories/GHSA-vm2f-46xc-5jc3
advisory
Sources
- CVE List CVE-2025-57697
- GitHub Advisory GHSA-vm2f-46xc-5jc3
- NVD CVE-2025-57697
- OSV PYSEC-2026-1197
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.