# CVE-2026-75602: OpenList: Authenticated arbitrary file write via Content-Disposition path traversal in SimpleHttp offline-download tool

> Authenticated users can exploit path traversal in the offline-download tool to overwrite arbitrary files, potentially leading to code execution.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2026
- **Updated:** 5 Sep 2026
- **Also known as:** GHSA-h6cj-26g5-67fv, GO-2026-6368

## What is CVE-2026-75602?

CVE-2026-75602 is a medium-severity path traversal vulnerability in OpenListTeam OpenList, published on 3 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

OpenList a file list program that supports multiple storage. Prior to 4.2.3, OpenList's offline-download feature at POST /api/fs/add_offline_download with tool: "SimpleHttp" accepts an attacker-supplied URL and saves its bytes under a per-task temporary directory before transferring them to the user's destination storage. The temporary filename comes from the attacker-controlled Content-Disposition header, is passed from parseFilenameFromContentDisposition in internal/offline_download/http/util.go to filepath.Join(task.TempDir, filename) in SimpleHttp.Run in internal/offline_download/http/client.go, and is opened with os.Create without a containment check. Because filepath.Join cleans .. segments, a non-admin user with PermAddOfflineDownload on any path can traverse out of task.TempDir and create, truncate, or overwrite any file writable by the OpenList process whose parent directory already exists. The server/handles/offline_download.go AddOfflineDownload route uses normal user authentication rather than AuthAdmin, and local-storage destinations fall through tryPutUrl in internal/offline_download/tool/add.go to the vulnerable SimpleHttp.Run path. This issue is fixed in version 4.2.3.

Weakness: CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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


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

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

Upgrade github.com/OpenListTeam/OpenList to 4.2.3 or later.

## Is CVE-2026-75602 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75602 is a medium-severity path traversal vulnerability in OpenListTeam OpenList, published on 3 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75602 exists.

Affected packages and fixed versions:
- github.com/OpenListTeam/OpenList (Go): affected all versions; no fix listed
- github.com/OpenListTeam/OpenList (Go): affected all versions; fixed in 4.2.3
- github.com/OpenListTeam/OpenList (Go): affected all versions; fixed in 4.2.3
- github.com/OpenListTeam/OpenList/v3 (Go): affected all versions; no fix listed
- github.com/OpenListTeam/OpenList/v4 (Go): affected all versions; fixed in 4.2.3

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-75602/ (Markdown: https://insights.sbomify.com/CVE-2026-75602/index.md)
```

## Sources

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

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