CVE-2026-102663: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor in OpenListTeam OpenList
Description
OpenList versions prior to 4.2.4 contain a vulnerability in the search API where a non-separator-aware prefix check allows restricted users to access metadata or existence information of files outside their authorized BasePath. This occurs because the strings.HasPrefix comparison incorrectly treats sibling paths as contained within the BasePath, leading to unauthorized exposure of file metadata and search result counts. The issue is resolved in version 4.2.4.
CVSS v3.1
Score 4.3medium
Affected software
OpenListTeam
OpenList
pkg:github/openlistteam/OpenListRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
OpenList's search API prior to version 4.2.4 uses a strings.HasPrefix comparison to authorize access to globally indexed Bleve search results against a restricted user's BasePath. This check is not separator-aware, causing sibling paths (e.g., /base2) to be incorrectly considered as contained within the BasePath (e.g., /base). As a result, restricted authenticated users can obtain unauthorized file metadata or file-existence information from sibling paths. Additionally, the backend Total value may reveal matches even if individual results are filtered out by other access controls. This vulnerability is classified as CWE-200 (Exposure of Sensitive Information) and CWE-639 (Authorization Bypass Through User-Controlled Key). The issue is fixed in OpenList version 4.2.4.
Potential Impact
An attacker with restricted authenticated access can gain unauthorized exposure to sensitive file metadata and existence information from sibling paths outside their authorized BasePath. This information disclosure does not allow modification or deletion of data but can reveal the presence of files and search result counts that should be inaccessible. The CVSS score is 4.3 (medium severity), reflecting limited confidentiality impact without integrity or availability effects.
Mitigation Recommendations
Upgrade OpenList to version 4.2.4 or later, where the issue is fixed. Prior to upgrading, no other vendor-provided mitigations are documented. Patch status is confirmed fixed in 4.2.4.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-09-29T15:56:02.102Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6acd2f242cdf04f656c3e8b2
Added to database: 10/12/2026, 19:04:04 UTC
Last enriched: 10/12/2026, 19:19:07 UTC
Last updated: 10/12/2026, 19:19:07 UTC
Views: 10
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.