cve.bz

CVE-2026-69160 openlistteam openlist

6.5 mediumEPSS 0.4%Fix available

Medium (6.5) in openlistteam openlist. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/OpenListTeam/OpenList/v4 4.2.4.

On this page
OpenList a file list program that supports multiple storage. Prior to 4.2.4, the share creation and update checks in server/handles/sharing.go use strings.HasPrefix(requested_path, user.BasePath) without enforcing a directory separator boundary. An authenticated user with CanShare permission and a BasePath such as /base can submit a sibling path such as /base2/secret.txt, create a share for the out-of-scope file, and use the public share download or list handlers to read data outside the assigned directory. This issue is fixed in version 4.2.4.

Severity

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-08-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-639 Authorization Bypass Through User-Controlled Key
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • github.com/OpenListTeam/OpenList/v4 (Go): fixed in 4.2.4

Ask an AI about this CVE

Show the promptExplain CVE-2026-69160 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-69160?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-69160?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-69160 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
OpenListTeam OpenList< 4.2.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-86cx-wwf4-phq4Gogithub.com/OpenListTeam/OpenList/v4<4.2.44.2.4
GO-2026-6109Gogithub.com/OpenListTeam/OpenListall versionsno fix published
GO-2026-6109Gogithub.com/OpenListTeam/OpenList/v3all versionsno fix published
GO-2026-6109Gogithub.com/OpenListTeam/OpenList/v4<4.2.44.2.4

References

Check your stackJSON