CVE-2026-102663 json
OpenList: Search metadata/count disclosure via Non-Separator-Aware Path Check in Bleve Search
published 3mo ago modified 27d ago also EUVD-2026-97775 , GHSA-p6ph-3jx2-3337 , GO-2026-6113
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
OpenList is a file list program that supports multiple storage backends. Prior to 4.2.4, the OpenList search API uses a non-separator-aware strings.HasPrefix comparison as a path containment authorization check when authorizing globally indexed Bleve results against a restricted user's BasePath. When Bleve search is enabled and a restricted authenticated user searches the global index for content in a sibling path, the user causes a globally indexed sibling-path result to pass the prefix check. The strings.HasPrefix(node.Parent, user.BasePath) predicate allows a sibling path such as /base2 to be treated as contained by /base. Unauthorized file metadata or file-existence information can be disclosed, and the backend Total value can reveal a match even when another access check removes the individual result. This issue is fixed in version 4.2.4.
Patch / fix
- go github.com/OpenListTeam/OpenList/v4 4.2.4
- oplist openlist 4.2.4
Is CVE-2026-102663 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 27d ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/OpenListTeam/OpenList/security/advisories/GHSA-p6ph-3jx2-3337 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/OpenListTeam/OpenList/v4 | <4.2.4 |
4.2.4 |
| go | github.com/OpenListTeam/OpenList | all versions |
no fix listed |
| go | github.com/OpenListTeam/OpenList/v3 | all versions |
no fix listed |
Affected products
- OpenListTeam OpenList
Classification
References
-
github.com
/OpenListTeam/OpenList/commit/59bd3431408578f420895457554700cc9a52375a
web, patch
-
github.com
/OpenListTeam/OpenList/commit/84ecda35aae2bd0020474086e6ddfd3aa2340679
web, patch
-
github.com
/OpenListTeam/OpenList/security/advisories/GHSA-p6ph-3jx2-3337
exploit, web, advisory
-
github.com
/OpenListTeam/OpenList/releases/tag/v4.2.4
web
-
github.com
/OpenListTeam/OpenList
package
Sources
- CVE List CVE-2026-102663
- GitHub Advisory GHSA-p6ph-3jx2-3337
- NVD CVE-2026-102663
- OSV GO-2026-6113
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.