CVE-2026-73509: OpenList: Authenticated users can rename files outside their base path via batch rename `src_name` traversal
OpenList a file list program that supports multiple storage. Prior to 4.2.4, the authenticated /api/fs/batchrename handler in server/handles/fsbatch.go authorizes only the source directory produced by user.JoinPath(req.SrcDir) and validates renameObject.NewName with checkRelativePath, but does not validate attacker-controlled renameObject.SrcName, supplied as srcname, before concatenating it with the authorized path and passing the result to fs.Rename. A user with rename permission can use traversal segments in srcname to make path normalization select a file outside the authorized directory and configured base path, resulting in cross-user file integrity loss, limited availability impact, and file-existence disclosure through success or error responses. This issue is fixed in version 4.2.4.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
OpenList (server/handles/fsbatch.go /api/fs/batch_rename handler)to a version that resolves this vulnerability.Fixed in 4.2.4
Event History
Frequently Asked Questions
What is the severity of CVE-2026-73509?
CVE-2026-73509 has a severity rating of 7.6, which is classified as high.
How do I fix CVE-2026-73509?
To mitigate CVE-2026-73509, upgrade to OpenList version 4.2.4 or later.
What type of vulnerability is CVE-2026-73509?
CVE-2026-73509 is a path traversal vulnerability affecting the batch rename functionality.
Who is affected by CVE-2026-73509?
Authenticated users of OpenList prior to version 4.2.4 are at risk from CVE-2026-73509.
What impact does CVE-2026-73509 have?
CVE-2026-73509 allows authenticated users to rename files outside their designated base path.