CVE-2026-25161: AlistGo alist · Path Traversal
Affects AlistGo alistSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 3.57.0 soon.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 56% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.57.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 4 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Upgrade alist and alistgo/alist to 3.57.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| AlistGoalist | Affected
| Fixed in
|
GitHubalistgo/alistpkg:github/alistgo/alistOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The primary mitigation is to upgrade all affected alist instances to version 3.57.0 or later, where the vulnerability is patched. Organizations should audit and restrict user permissions rigorously to minimize the number of users with file operation privileges. Implement strong authentication mechanisms, including multi-factor authentication, to reduce the risk of compromised accounts. Conduct thorough logging and monitoring of file operations to detect suspicious activities indicative of traversal exploitation. Employ network segmentation and access controls to limit exposure of alist services to trusted users and networks. Additionally, perform regular security assessments and penetration testing focusing on file operation handlers. If upgrading immediately is not feasible, consider deploying web application firewalls (WAFs) with custom rules to detect and block traversal sequences in file operation requests. Finally, educate users about the risks of path traversal and enforce strict input validation policies.
Description
CVE-2026-25161 is a high-severity path traversal vulnerability in AlistGo's alist software versions prior to 3.57.0. It allows an authenticated attacker to bypass directory-level authorization by injecting traversal sequences into file names, enabling unauthorized file operations such as removal, movement, and copying across user boundaries within the same storage mount. The vulnerability affects multiple file operation handlers and compromises confidentiality, integrity, and availability of data. No user interaction is required beyond authentication, and the flaw has been patched in version 3.57.0. There are no known exploits in the wild yet. European organizations using vulnerable versions of alist are at risk, especially those relying on this software for file management across multiple storage backends.