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.
- 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
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
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 | 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.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-54093 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54093 exists.
Sources
Also known as GHSA-gxjx-7m74-hcq8, GO-2026-5411.