Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73509 high CVSS 7.6

Path Traversal in github.com/OpenListTeam/OpenList/v4 (CVE-2026-73509)

Summary

Path traversal in github.com/OpenListTeam/OpenList/v4 (CVE-2026-73509). Data can be tampered with by attackers. Exploitable via new_name. Mitigation: upgrade to 4.2.4 or later.

Original description

The description as published by the source.

Summary

The /api/fs/batch_rename handler validates and authorizes only the requested source directory. It rejects path separators in new_name, but it does not validate src_name. The handler concatenates src_dir and attacker-controlled src_name, then passes the result to the filesystem rename layer, where the path is normalized.

An authenticated user with rename permission can set src_name to traversal segments such as ../../ab/secret.txt. When the user's base path is /team/a and src_dir is /writable, the authorized directory becomes /team/a/writable, but the final source path normalizes to /team/ab/secret.txt. The file outside the user's base path is then renamed.

Details

The HTTP API registers filesystem management routes under the authenticated group:

  • server/router.go:104 registers _fs(auth.Group("/fs")).
  • server/router.go:198 through server/router.go:205 expose /api/fs/batch_rename.

The vulnerable code is in server/handles/fsbatch.go:

  • src_dir is constrained through user.JoinPath(req.SrcDir) (server/handles/fsbatch.go:170 through server/handles/fsbatch.go:174).
  • Write permission is checked only for that constrained directory (server/handles/fsbatch.go:176 through server/handles/fsbatch.go:185).
  • The loop checks renameObject.NewName with checkRelativePath, but does not check renameObject.SrcName (server/handles/fsbatch.go:186 through server/handles/fsbatch.go:194).
  • The handler builds `filePath…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-73509 has been found in github.com/OpenListTeam/OpenList/v4.
Attackers can target a specific entry point like new_name over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.6/10.
What to do: upgrade github.com/OpenListTeam/OpenList/v4 to 4.2.4 or later.
If unsure, ask your IT team or search "github.com/OpenListTeam/OpenList/v4 CVE-2026-73509" on the vendor's site.

CVE-2026-73509 (github.com/OpenListTeam/OpenList/v4) — CWE-22 / CVSS v3 7.6
Attack vector: remote (network-reachable) / no user interaction
Attack surface: new_name / src_name / src_dir / renameObject.NewName
Patched: 4.2.4 — 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/OpenListTeam/OpenList/v4. Attackers reach the vulnerable code path via new_name.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/OpenListTeam/OpenList/v4. Attack surface: new_name / src_name / src_dir / renameObject.NewName.

🔥 Severity

Severity: High (CVSS 7.6/10). Data can be tampered with by attackers.

🔧 How to fix

Update to 4.2.4.

🛡️ 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/OpenListTeam/OpenList/v4' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/OpenListTeam/OpenList/v4' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/OpenListTeam/OpenList/v4 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/OpenListTeam/OpenList/v4 to 4.2.4

    ステージング環境で 4.2.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/OpenListTeam/OpenList/v4
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"4.2.4"}]}]
Go github.com/OpenListTeam/OpenList
[{"type":"SEMVER","events":[{"introduced":"0"}]}]
Go github.com/OpenListTeam/OpenList/v3
[{"type":"SEMVER","events":[{"introduced":"0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details