Is CVE-2026-25161 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-25161 being exploited in the wild.

How severe is CVE-2026-25161?

High severity, with a CVSS score of 8.8, published 4 February 2026.

Which products and versions are affected?

AlistGo Alist < 3.57.0; github.com/alist-org/alist (Go) SEMVER:introduced=0; github.com/alist-org/alist/v3 (Go) < 3.57.0, SEMVER:introduced=0,fixed=3.57.0.

Is there a fix for CVE-2026-25161?

Yes. github.com/alist-org/alist/v3 (Go): upgrade to 3.57.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-25161 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-25161?

Check whether you run AlistGo Alist, github.com/alist-org/alist (Go) or github.com/alist-org/alist/v3 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-25161: Alist path traversal in multiple file operation handlers

Q: Which products and versions are affected?

AlistGo Alist < 3.57.0; github.com/alist-org/alist (Go) SEMVER:introduced=0; github.com/alist-org/alist/v3 (Go) < 3.57.0, SEMVER:introduced=0,fixed=3.57.0.

Q: Is there a fix for CVE-2026-25161?

Yes. github.com/alist-org/alist/v3 (Go): upgrade to 3.57.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-25161 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-25161?

Check whether you run AlistGo Alist, github.com/alist-org/alist (Go) or github.com/alist-org/alist/v3 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-25161 · Severity: high · CVSS 8.8 · Published 2026-02-04

Alist, a file list program that supports multiple storage backends, is vulnerable to a security flaw that allows users to access files they shouldn't see. An authenticated user can use specially crafted file names to "jump" out of their assigned folder and delete, move, or copy files belonging to other users or administrators. This could lead to the loss of sensitive data or unauthorized modification of files on shared storage systems.

Technologies: github.com/alist-org/alist (Go), github.com/alist-org/alist/v3 (Go). Vendors: Go.

Quick answers

Is CVE-2026-25161 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-25161 being exploited in the wild.
How severe is CVE-2026-25161?: High severity, with a CVSS score of 8.8, published 4 February 2026.
Which products and versions are affected?: AlistGo Alist < 3.57.0; github.com/alist-org/alist (Go) SEMVER:introduced=0; github.com/alist-org/alist/v3 (Go) < 3.57.0, SEMVER:introduced=0,fixed=3.57.0.
Is there a fix for CVE-2026-25161?: Yes. github.com/alist-org/alist/v3 (Go): upgrade to 3.57.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-25161 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-25161?: Check whether you run AlistGo Alist, github.com/alist-org/alist (Go) or github.com/alist-org/alist/v3 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/alist-org/alist/v3 (Go): upgrade to 3.57.0 or later
```
go get github.com/alist-org/alist/v3@v3.57.0
```

Technical details

A path traversal vulnerability (CWE-22) exists in Alist's file operation handlers, specifically within 'server/handles/fsmanage.go' and 'server/handles/fsbatch.go'. The application fails to properly sanitize filename components in 'req.Names', 'renameObject.SrcName', and 'renameObject.NewName' before concatenating them with directory paths using 'stdpath.Join()' or 'fmt.Sprintf()'. An authenticated attacker can inject '../' sequences to escape their assigned base path. This enables unauthorized file operations (remove, copy, rename, move) across user boundaries within the same storage mount. The issue is fixed in version 3.57.0.

Affected products

AlistGo alist < 3.57.0

Identifiers

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

Timeline

2026-02-04: disclosed
2026-02-04: advisory
2026-02-04: patched: Fixed in version 3.57.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.