All vulnerabilities
CVE-2026-102663GHSA-p6ph-3jx2-3337GO-2026-6113

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

OpenListTeam OpenListGoLibraries & packages
CVSS
4.3Medium
ExploitationPublic exploit codeCISA's assessment says proof of concept code is public, assessed 13 Oct 2026. Not in the KEV catalogCISA via CVE List
Exploit odds (EPSS)0.21%Chance of exploitation activity in the next 30 days, higher than 10% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in4.2.4Fixed versionOSV
Published12 Oct 2026Updated 13 Oct 2026CVE List

What fixes it

  • 4.2.4github.com/OpenListTeam/OpenList/v4, GoOSVgo get github.com/OpenListTeam/OpenList/v4@v4.2.4

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

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.

Text from CVE List

Affected versions 2

  • OpenListaffected: < 4.2.4CVE List
  • github.com/OpenListTeam/OpenList/v4, Gofrom first release, fixed in 4.2.4OSV

References 4