Skip to content
Fencer Vulns
medium 6.5

CVE-2026-69160 json

OpenList: Arbitrary File Read via Path Prefix Confusion in Share Creation API

published 2026-07-24 3 mo ago modified 2026-10-22 17 d ago also GHSA-86cx-wwf4-phq4 , GO-2026-6109 , EUVD-2026-61101

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 34%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/OpenListTeam/OpenList/v4 4.2.4

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
2 mo ago

Exploit prediction

0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/OpenListTeam/OpenList/security/advisories/GHSA-86cx-wwf4-phq4 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key

References

Sources

Fencer Vulns 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.