Answer in brief
CVE-2026-73509 records a High severity (CVSS 7.6) vulnerability in OpenList: Authenticated users can rename files outside their base path via batch rename `src_name` traversal. The current sources do not mark it as known exploited. The current feed maps OpenListTeam/OpenList (generic), github.com/OpenListTeam/OpenList/v4 (go), github.com/OpenListTeam/OpenList/v4 (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-73509 records a High severity (CVSS 7.6) vulnerability in OpenList: Authenticated users can rename files outside their base path via batch rename `src_name` traversal. The current sources do not mark it as known exploited. The current feed maps OpenListTeam/OpenList (generic), github.com/OpenListTeam/OpenList/v4 (go), github.com/OpenListTeam/OpenList/v4 (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.6. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps OpenListTeam/OpenList (generic), github.com/OpenListTeam/OpenList/v4 (go), github.com/OpenListTeam/OpenList/v4 (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| OpenListTeam/OpenListgeneric | < 4.2.4 | Not reported |
| github.com/OpenListTeam/OpenList/v4go | >=0 <4.2.4 | 4.2.4 |
| github.com/OpenListTeam/OpenList/v4go | <=4.2.3 | 4.2.4 |
Published upstream
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 8, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.6. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps OpenListTeam/OpenList (generic), github.com/OpenListTeam/OpenList/v4 (go), github.com/OpenListTeam/OpenList/v4 (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| OpenListTeam/OpenListgeneric | < 4.2.4 | Not reported |
| github.com/OpenListTeam/OpenList/v4go | >=0 <4.2.4 | 4.2.4 |
| github.com/OpenListTeam/OpenList/v4go | <=4.2.3 | 4.2.4 |
Published upstream
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 8, 2026
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.
Quoted source text, attributed separately from HOL analysis.