# CVE-2026-25059: OpenList affected by Path Traversal in file copy and remove handlers

> Authenticated attackers can bypass directory restrictions via path traversal to access, delete, or copy other users' files within the same storage mount.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 2 Feb 2026
- **Updated:** 4 Feb 2026
- **Also known as:** GHSA-qmj2-8r24-xxcq, GO-2026-4396

## What is CVE-2026-25059?

CVE-2026-25059 is a high-severity path traversal vulnerability in OpenListTeam OpenList, published on 2 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenList Frontend is a UI component for OpenList. Prior to 4.1.10, the application contains path traversal vulnerability in multiple file operation handlers in server/handles/fsmanage.go. Filename components in req.Names are directly concatenated with validated directories using stdpath.Join. This allows ".." sequences to bypass path restrictions, enabling users to access other users' files within the same storage mount and perform unauthorized actions such as deletion, renaming, or copying of files. An authenticated attacker can bypass directory-level authorisation by injecting traversal sequences into filename components, enabling unauthorised file removal and copying across user boundaries within the same storage mount. This vulnerability is fixed in 4.1.10.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

5 open source packages ship an affected version, including github.com/OpenListTeam/OpenList/v4, github.com/OpenListTeam/OpenList and github.com/OpenListTeam/OpenList/v3. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/OpenListTeam/OpenList/v4` | Go | All versions | 4.1.10 |
| `github.com/OpenListTeam/OpenList/v4` | Go | All versions | 4.1.10 |
| `github.com/OpenListTeam/OpenList/v4` | Go | All versions | 4.1.10 |
| `github.com/OpenListTeam/OpenList` | Go | All versions | None |
| `github.com/OpenListTeam/OpenList/v3` | Go | All versions | None |

Products: Oplist Openlist.

## How do I fix CVE-2026-25059?

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

## Is CVE-2026-25059 being exploited?

There is no known exploitation of CVE-2026-25059 in the wild and no public exploit code.

## Other vulnerabilities in OpenListTeam OpenList

- [CVE-2026-25060](https://insights.sbomify.com/CVE-2026-25060/): OpenList Insecure TLS Default Configuration (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-25059 is a high-severity path traversal vulnerability in OpenListTeam OpenList, published on 2 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-25059 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/OpenListTeam/OpenList/v4 (Go): affected all versions; fixed in 4.1.10
- github.com/OpenListTeam/OpenList/v4 (Go): affected all versions; fixed in 4.1.10
- github.com/OpenListTeam/OpenList/v4 (Go): affected all versions; fixed in 4.1.10
- 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-25059/ (Markdown: https://insights.sbomify.com/CVE-2026-25059/index.md)
```

## Sources

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

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