CVE-2026-69160: CWE-639: Authorization Bypass Through User-Controlled Key in OpenListTeam OpenList
OpenList a file list program that supports multiple storage. Prior to 4.2.4, the share creation and update checks in server/handles/sharing.go use strings.HasPrefix(requested_path, user.BasePath) without enforcing a directory separator boundary. An authenticated user with CanShare permission and a BasePath such as /base can submit a sibling path such as /base2/secret.txt, create a share for the out-of-scope file, and use the public share download or list handlers to read data outside the assigned directory. This issue is fixed in version 4.2.4.
AI Analysis
Technical Summary
OpenList, a file listing program supporting multiple storage backends, has an authorization bypass vulnerability (CWE-639) in versions before 4.2.4. The vulnerability arises because the server's share creation and update logic uses a naive prefix check (strings.HasPrefix) on requested paths without enforcing directory separator boundaries. This allows an authenticated user with CanShare permission and a base path like /base to create shares for sibling paths such as /base2/secret.txt, effectively bypassing directory restrictions and accessing files outside their assigned directory. The vulnerability is addressed in OpenList version 4.2.4.
Potential Impact
An authenticated user with sharing permissions can bypass directory restrictions and create shares for files outside their authorized base directory. This leads to unauthorized disclosure of potentially sensitive files via public share download or listing handlers. The vulnerability does not affect confidentiality beyond unauthorized read access and does not impact integrity or availability.
Mitigation Recommendations
Upgrade OpenList to version 4.2.4 or later, where the issue is fixed. No other mitigation or temporary workaround is documented. Patch status is confirmed fixed in 4.2.4.
CVE-2026-69160: CWE-639: Authorization Bypass Through User-Controlled Key in OpenListTeam OpenList
Description
OpenList a file list program that supports multiple storage. Prior to 4.2.4, the share creation and update checks in server/handles/sharing.go use strings.HasPrefix(requested_path, user.BasePath) without enforcing a directory separator boundary. An authenticated user with CanShare permission and a BasePath such as /base can submit a sibling path such as /base2/secret.txt, create a share for the out-of-scope file, and use the public share download or list handlers to read data outside the assigned directory. This issue is fixed in version 4.2.4.
CVSS v3.1
Score 6.5medium
Affected software
pkg:github/openlistteam/OpenListRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
OpenList, a file listing program supporting multiple storage backends, has an authorization bypass vulnerability (CWE-639) in versions before 4.2.4. The vulnerability arises because the server's share creation and update logic uses a naive prefix check (strings.HasPrefix) on requested paths without enforcing directory separator boundaries. This allows an authenticated user with CanShare permission and a base path like /base to create shares for sibling paths such as /base2/secret.txt, effectively bypassing directory restrictions and accessing files outside their assigned directory. The vulnerability is addressed in OpenList version 4.2.4.
Potential Impact
An authenticated user with sharing permissions can bypass directory restrictions and create shares for files outside their authorized base directory. This leads to unauthorized disclosure of potentially sensitive files via public share download or listing handlers. The vulnerability does not affect confidentiality beyond unauthorized read access and does not impact integrity or availability.
Mitigation Recommendations
Upgrade OpenList to version 4.2.4 or later, where the issue is fixed. No other mitigation or temporary workaround is documented. Patch status is confirmed fixed in 4.2.4.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-03T15:47:09.655Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a84a24cc6e8be033294f6b3
Added to database: 08/18/2026, 18:19:56 UTC
Last enriched: 08/18/2026, 18:38:39 UTC
Last updated: 09/05/2026, 22:52:12 UTC
Views: 59
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.