CVE-2026-25161 is a high-severity (CVSS 8.8) Path Traversal vulnerability in github.com/alist-org/alist/v3. A fix is available for github.com/alist-org/alist/v3 — see the affected versions and patch details below.
Alist vulnerable to Path Traversal in multiple file operation handlers
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-25161.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/alist-org/alist/v3Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Summary
The application contains a Path Traversal vulnerability (CWE-22) in multiple file operation handlers. An authenticated attacker can bypass directory-level authorisation by injecting traversal sequences into filename components, enabling unauthorised file removal, movement and copying across user boundaries within the same storage mount.
Details
The application contains a Path Traversal vulnerability (CWE-22) in multiple file operation handlers (server/handles/fsmanage.go, server/handles/fsbatch.go, etc.). Filename components in req.Names, renameObject.SrcName, and renameObject.NewName are directly concatenated with validated directories using stdpath.Join() or fmt.Sprintf(). This allows ".." sequences to bypass path restrictions, enabling users to access other users' files within the same storage mount and perform unauthorized actions such as deletion, renaming, or copying of files.
func FsRemove(c *gin.Context) {
// ...
for _, name := range req.Names {
err := fs.Remove(c, stdpath.Join(reqDir, name))
func FsCopy(c *gin.Context) {
// ...
for i, name := range req.Names {
t, err := fs.Copy(c, stdpath.Join(srcDir, name), dstDir, len(req.Names) > i+1)
func FsBatchRename(c *gin.Context) {
// ...
for _, renameObject := range req.RenameObjects {
filePath := fmt.Sprintf("%s/%s", reqPath, renameObject.SrcName) // Vulnerable concatenation ✗
fs.Rename(c, filePath, renameObject.NewName)
}
}
PoC
- Environment setup:
- Storage mount '/shared' configured with multiple users.
- Alice has base path '/shared/alice'.
- Admin has base path '/shared/admin' with private files.
- Both users operate within the same storage mount.
- Craft Malicious Request: Alice sends a POST request to /api/fs/remove containing a filename with '../' in it.
curl -X POST -H "Content-Type: application/json" -d '{"dir":"/","names":["../admin/private.txt"]}' http://localhost:5244/api/fs/remove
Admin's file is deleted without Alice having authorisation for Admin's directory.
Impact
This vulnerability enables privilege escalation within shared storage environments. An authenticated attacker with basic file operation permissions (remove/rename/copy/move) can bypass directory-level authorisation controls when multiple users exist within the same storage mount.
Attack Requirements:
- Authenticated user account (not guest)
- Basic file operation permissions
- Multi-user environment within the same storage mount
Consequences:
- Unauthorised data access: Read, copy, and exfiltrate files from other users' directories
- Data destruction: Delete or rename files belonging to other users
- Access control bypass: Circumvent directory isolation mechanisms
- Integrity violation: Modify or move files across user boundaries
Credit
This vulnerability was discovered by:
- XlabAI Team of Tencent Xuanwu Lab
- Atuin Automated Vulnerability Discovery Engine
If there are questions regarding the vulnerability details, please feel free to reach out for further discussion at [email protected].
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/alist-org/alist/v3 | all versions | 3.57.0go get github.com/alist-org/alist/v3@v3.57.0 |
Affected Products
alistalistgoDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/alist-org/alist/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/alist-org/alist/v3 to 3.57.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-25161 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2026-25161 in your dependencies?
Find it across Go, including transitive dependencies.