Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

GHSA-x4q4-7phh-42j9

HIGH

Alist vulnerable to Path Traversal in multiple file operation handlers

Also known asCVE-2026-25161GO-2026-4415
Published
Feb 4, 2026
Updated
Feb 5, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk49th percentile+0.69%
0.00%0.41%0.81%1.22%0.0%0.0%0.0%0.0%0.7%Mar 26May 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected
🐹github.com/alist-org/alist/v3

Real-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.

FsRemove:

func FsRemove(c *gin.Context) {
	// ...
	for _, name := range req.Names {
		err := fs.Remove(c, stdpath.Join(reqDir, name))

FsCopy:

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:

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.
  1. 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.

Video

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 [email protected].

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/alist-org/alist/v3all versions3.57.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/alist-org/alist/v3. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. 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 GHSA-x4q4-7phh-42j9 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-x4q4-7phh-42j9 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-x4q4-7phh-42j9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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
O3 Security · Impact-Aware SCA

Is GHSA-x4q4-7phh-42j9 in your dependencies?

O3 detects GHSA-x4q4-7phh-42j9 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-x4q4-7phh-42j9: v3 Path Traversal (High 8.8) | O3 Security