CVE-2026-73509
Received Received - Intake

Authenticated Path Traversal in OpenList File List Program

Publication date: 2026-08-13

Last updated on: 2026-08-13

Assigner: GitHub, Inc.

Description
OpenList a file list program that supports multiple storage. Prior to 4.2.4, the authenticated /api/fs/batch_rename 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 src_name, before concatenating it with the authorized path and passing the result to fs.Rename. A user with rename permission can use traversal segments in src_name 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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-13
Last Modified
2026-08-13
Generated
2026-08-13
AI Q&A
2026-08-13
EPSS Evaluated
N/A
NVD
CVE-2026-73509
EUVD
EUVD-2026-58087

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
openlistteam openlist to 4.2.4 (exc)
openlist openlist to 4.2.4 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is a path traversal vulnerability in OpenList's batch rename feature. Authenticated users with rename permissions can manipulate the source file path parameter to escape their authorized directory by using traversal sequences like ../../. The application validates the destination path but fails to validate the source path, allowing attackers to rename files outside their restricted directory. This affects file integrity and could impact other users' files.

Detection Guidance

To detect this vulnerability, check if your OpenList instance is running a version prior to 4.2.4. Use commands like 'curl -s http://your-openlist-server/api/version' or inspect the server logs for batch rename API calls with suspicious src_name parameters containing path traversal sequences like '../'.

Impact Analysis

If exploited, this vulnerability could allow an attacker to rename files outside their authorized directory. This may result in file integrity loss, limited availability issues for affected files, and potential disclosure of file existence through success or error responses. The impact is limited to users with rename permissions in versions prior to 4.2.4.

Mitigation Strategies

Immediately upgrade OpenList to version 4.2.4 or later. If upgrading is not possible, restrict access to the /api/fs/batch_rename endpoint for users without rename permissions and monitor for unauthorized file operations.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-73509. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart