Loading...
Skip to main content

CVE-2026-25161 — Alist vulnerable to Path Traversal in...

HIGH

Alist vulnerable to Path Traversal in multiple file operation handlers

Published February 4, 2026Updated February 5, 2026Source: osv

Summary

### 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](https://github.com/AlistGo/alist/blob/main/server/handles/fsmanage.go), [server/handles/fsbatch.go](https://github.com/AlistGo/alist/blob/main/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. [FsRemove](https://github.com/AlistGo/alist/blob/b4d9beb49cba399842a54fcc33bc95a4a09b7bd4/server/handles/fsmanage.go#L253-L254): ~~~go func FsRemove(c *gin.Context) { // ... for _, name := range req.Names { err := fs.Remove(c, stdpath.Join(reqDir, name)) ~~~ [FsCopy](https://github.com/AlistGo/alist/blob/b4d9beb49cba399842a54fcc33bc95a4a09b7bd4/server/handles/fsmanage.go#L165-L166): ~~~go 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) ~~~ [FsBatchRename](https://github.com/AlistGo/alist/blob/b4d9beb49cba399842a54fcc33bc95a4a09b7bd4/server/handles/fsbatch.go#L188-L189): ~~~go 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 1. 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. 2. Craft Malicious Request: Alice sends a POST request to _/api/fs/remove_ containing a filename with '../' in it. ~~~bash 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. [Video](https://github.com/user-attachments/assets/5789fa36-c82c-4781-a5f7-145f54689ada) ### 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: 1. Authenticated user account (not guest) 2. Basic file operation permissions 3. Multi-user environment within the same storage mount #### Consequences: 1. Unauthorised data access: Read, copy, and exfiltrate files from other users' directories 2. Data destruction: Delete or rename files belonging to other users 3. Access control bypass: Circumvent directory isolation mechanisms 4. 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 xlabai@tencent.com.

Advisory Timeline

  • First published February 4, 2026 (250 days ago).
  • Last revised February 5, 2026 — 1 day after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Go
Update github.com/alist-org/alist/v3 to 3.57.0 or later
go get github.com/alist-org/alist/v3@v3.57.0

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (1)

Affects 1 ecosystem: go (1).

PackageEcosystemAffectedFixed In
github.com/alist-org/alist/v3
go
All versions3.57.0

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 8.8 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Frequently Asked Questions

What is CVE-2026-25161?
Alist vulnerable to Path Traversal in multiple file operation handlers This vulnerability has been assigned a severity rating of HIGH (CVSS score: 8.8/10).
How do I check if my project is affected by CVE-2026-25161?
CVE-2026-25161 affects github.com/alist-org/alist/v3. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-25161 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
8.8

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-x4q4-7phh-42j9
GO-2026-4415

Related CVEs

  • CVE-2026-25160
    CRITICAL

    Alist has Insecure TLS Config

  • CVE-2026-107809
    HIGH

    Nginx-UI AuthRequired token cookie fallback enables CSRF against management APIs

  • CVE-2026-107813
    HIGH

    Nginx UI: Incomplete fix of CVE-2026-84315 - the api/cluster router was not - wrapped in RequireSecureSession, so those sensitive mutations run without OTP step-up

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies