← Back
CVE-2026-25161
Path Traversal in github.com/alist-org/alist/v3 (CVE-2026-25161)
Summary
path traversal in github.com/alist-org/alist/v3 (CVE-2026-25161). Risk of unauthorized operations or information disclosure. Exploitable via ``req.Names``. Mitigation: upgrade to `3.57.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-25161** has been found in github.com/alist-org/alist/v3.
Attackers can target a specific entry point like ``req.Names`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade github.com/alist-org/alist/v3 to **3.57.0** or later.
If unsure, ask your IT team or search "github.com/alist-org/alist/v3 CVE-2026-25161" on the vendor's site.
CVE-2026-25161 (github.com/alist-org/alist/v3) — CWE-22 /
Attack surface: `req.Names` / `renameObject.SrcName` / `renameObject.NewName`
Patched: `3.57.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in github.com/alist-org/alist/v3. Attackers reach the vulnerable code path via ``req.Names`` without authentication.
📍 Affected scope
github.com/alist-org/alist/v3 — . Attack surface: `req.Names` / `renameObject.SrcName` / `renameObject.NewName`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.57.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'github.com/alist-org/alist/v3' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/alist-org/alist/v3' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `github.com/alist-org/alist/v3` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/alist-org/alist/v3 to 3.57.0ステージング環境で 3.57.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
github.com/alist-org/alist/v3
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.57.0"}]}]
References
- web https://github.com/AlistGo/alist/security/advisories/GHSA-x4q4-7phh-42j9
- web https://github.com/AlistGo/alist/commit/b188288525b9a35c76535139311e7c036dab057e
- web https://github.com/AlistGo/alist/blob/b4d9beb49cba399842a54fcc33bc95a4a09b7bd4/server/handles/fsbatch.go#L188-L189
- web https://github.com/AlistGo/alist/blob/b4d9beb49cba399842a54fcc33bc95a4a09b7bd4/server/handles/fsmanage.go#L165-L166
- web https://nvd.nist.gov/vuln/detail/CVE-2026-25161
- web https://github.com/advisories/GHSA-x4q4-7phh-42j9