# CVE-2026-102663: OpenList: Search metadata/count disclosure via Non-Separator-Aware Path Check in Bleve Search

> A restricted user can leak file metadata and existence information from sibling paths due to a flawed path containment check in the search API.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-p6ph-3jx2-3337, GO-2026-6113

## What is CVE-2026-102663?

CVE-2026-102663 is a medium-severity vulnerability in OpenListTeam OpenList, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-102663?

5 open source packages ship an affected version, including github.com/OpenListTeam/OpenList/v4, github.com/OpenListTeam/OpenList and github.com/OpenListTeam/OpenList/v3.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/OpenListTeam/OpenList/v4` | Go | All versions | 4.2.4 |
| `github.com/OpenListTeam/OpenList/v4` | Go | All versions | 4.2.4 |
| `github.com/OpenListTeam/OpenList/v4` | Go | All versions | 4.2.4 |
| `github.com/OpenListTeam/OpenList` | Go | All versions | None |
| `github.com/OpenListTeam/OpenList/v3` | Go | All versions | None |

## How do I fix CVE-2026-102663?

Upgrade github.com/OpenListTeam/OpenList/v4 to 4.2.4 or later.

## Is CVE-2026-102663 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102663 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102663 and fix it if it is affected.

What it is: CVE-2026-102663 is a medium-severity vulnerability in OpenListTeam OpenList, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102663 exists.

Affected packages and fixed versions:
- github.com/OpenListTeam/OpenList/v4 (Go): affected all versions; fixed in 4.2.4
- github.com/OpenListTeam/OpenList/v4 (Go): affected all versions; fixed in 4.2.4
- github.com/OpenListTeam/OpenList/v4 (Go): affected all versions; fixed in 4.2.4
- github.com/OpenListTeam/OpenList (Go): affected all versions; no fix listed
- github.com/OpenListTeam/OpenList/v3 (Go): affected all versions; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102663/ (Markdown: https://insights.sbomify.com/CVE-2026-102663/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102663
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102663
- OSV: https://osv.dev/vulnerability/CVE-2026-102663

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102663/
Summaries are generated and may contain mistakes; the official description above is the record.