Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Medium severity, with a CVSS score of 4.3, published 24 July 2026.

Which products and versions are affected?

github.com/OpenListTeam/OpenList/v4 (Go) <= 4.2.3; OpenListTeam OpenList <= 4.2.3.

Is there a fix for This vulnerability?

A patch was published on 2026-07-24: Fixed in version 4.2.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

It is attacked over the network, in a network appliance.

Check whether you run github.com/OpenListTeam/OpenList/v4 (Go) or OpenListTeam OpenList at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

OpenList authorization bypass and information disclosure in search API

Q: Is there a fix for This vulnerability?

A patch was published on 2026-07-24: Fixed in version 4.2.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is This vulnerability attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected?

Check whether you run github.com/OpenListTeam/OpenList/v4 (Go) or OpenListTeam OpenList at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Severity: medium · CVSS 4.3 · Published 2026-07-24

OpenList, a file storage and management application, contains a security flaw in its search functionality. An authenticated user can bypass directory restrictions to view file names and metadata in folders they are not authorized to access. This could lead to the exposure of sensitive internal documents or infrastructure details.

Technologies: github.com/OpenListTeam/OpenList/v4 (Go). Vendors: Go.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Medium severity, with a CVSS score of 4.3, published 24 July 2026.
Which products and versions are affected?: github.com/OpenListTeam/OpenList/v4 (Go) <= 4.2.3; OpenListTeam OpenList <= 4.2.3.
Is there a fix for This vulnerability?: A patch was published on 2026-07-24: Fixed in version 4.2.4 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked over the network, in a network appliance.
Am I affected?: Check whether you run github.com/OpenListTeam/OpenList/v4 (Go) or OpenListTeam OpenList at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability exists in the search handler (server/handles/search.go) due to an insecure path prefix validation using 'strings.HasPrefix'. Because the check is not path-separator aware, a user restricted to '/base' can access a sibling directory like '/base2'. Additionally, the Bleve search backend (internal/search/bleve/search.go) ignores path boundaries and returns a global 'Total' count. This allows attackers to perform blind data enumeration by observing search result counts for keywords even if file content is otherwise restricted. The issue is fixed in version 4.2.4 by implementing separator-aware path containment and backend-level filtering.

Affected products

OpenListTeam OpenList <= 4.2.3

Timeline

2026-07-23: disclosed
2026-07-24: patched: Fixed in version 4.2.4
2026-07-24: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.