# CVE-2026-73509: OpenList: Authenticated users can rename files outside their base path via batch rename `src_name` traversal

> Authenticated users can rename files outside their authorized directory via path traversal in the batch rename API, leading to data modification and information disclosure.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:L`)
- **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:** 13 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-95cv-r8x4-vh75, GO-2026-6110

## What is CVE-2026-73509?

CVE-2026-73509 is a high-severity path traversal vulnerability in OpenListTeam OpenList, published on 13 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 authenticated /api/fs/batch_rename handler in server/handles/fsbatch.go authorizes only the source directory produced by user.JoinPath(req.SrcDir) and validates renameObject.NewName with checkRelativePath, but does not validate attacker-controlled renameObject.SrcName, supplied as src_name, before concatenating it with the authorized path and passing the result to fs.Rename. A user with rename permission can use traversal segments in src_name to make path normalization select a file outside the authorized directory and configured base path, resulting in cross-user file integrity loss, limited availability impact, and file-existence disclosure through success or error responses. This issue is fixed in version 4.2.4.

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

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

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

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

## Is CVE-2026-73509 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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