# CVE-2026-69160: OpenList: Arbitrary File Read via Path Prefix Confusion in Share Creation API

> Authenticated users can read files outside their assigned directory by exploiting path prefix confusion in the share creation API.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** 18 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-86cx-wwf4-phq4, GO-2026-6109

## What is CVE-2026-69160?

CVE-2026-69160 is a medium-severity path traversal vulnerability in OpenListTeam OpenList, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

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-69160?

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

## Is CVE-2026-69160 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-69160 is a medium-severity path traversal vulnerability in OpenListTeam OpenList, published on 18 Aug 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-69160 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-69160/ (Markdown: https://insights.sbomify.com/CVE-2026-69160/index.md)
```

## Sources

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

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