# CVE-2026-54093: File Browser: Path traversal in download-as-zip/tar via Windows-style backslash separators in stored filenames

> An attacker can craft filenames with backslashes to cause arbitrary file writes on Windows victims when they download and extract archives.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** GHSA-gxjx-7m74-hcq8, GO-2026-5411

## What is CVE-2026-54093?

CVE-2026-54093 is a medium-severity path traversal vulnerability in filebrowser, published on 25 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. Prior to 2.63.6, filebrowser builds the download-as-zip / download-as-tar archive entry names with filepath.ToSlash, which on a Linux host is a no-op for backslashes (\ is only a path separator on Windows). A file whose name contains Windows-style traversal is accepted by the resource handlers, stored on the Linux filesystem with a literal backslash name, and then emitted verbatim as the archive entry name. Windows extractors interpret \ as a path separator and write the extracted file outside the extraction directory — arbitrary file write on the victim who downloads and extracts the archive. This vulnerability is fixed in 2.63.6.

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

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

6 open source packages ship an affected version, including github.com/filebrowser/filebrowser and github.com/filebrowser/filebrowser/v2.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/filebrowser/filebrowser` | Go | All versions | None |
| `github.com/filebrowser/filebrowser` | Go | All versions to 1.11.0 | None |
| `github.com/filebrowser/filebrowser` | Go | All versions to 1.11.0 | None |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.63.6 |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.63.6 |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.63.6 |

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

Upgrade to a fixed version.

## Is CVE-2026-54093 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54093 is a medium-severity path traversal vulnerability in filebrowser, published on 25 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54093 exists.

Affected packages and fixed versions:
- github.com/filebrowser/filebrowser (Go): affected all versions; no fix listed
- github.com/filebrowser/filebrowser (Go): affected all versions up to 1.11.0; no fix listed
- github.com/filebrowser/filebrowser (Go): affected all versions up to 1.11.0; no fix listed
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.63.6
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.63.6
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.63.6

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

## Sources

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

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