Path Traversal in github.com/filebrowser/filebrowser/v2 (CVE-2026-54093)
Summary
Path traversal in github.com/filebrowser/filebrowser/v2 (CVE-2026-54093). Risk of unauthorized operations or information disclosure. Exploitable via filepath.ToSlash. Mitigation: upgrade to 2.63.6 or later.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-54093 has been found in github.com/filebrowser/filebrowser/v2.
Attackers can target a specific entry point like filepath.ToSlash over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/filebrowser/filebrowser/v2 to 2.63.6 or later.
If unsure, ask your IT team or search "github.com/filebrowser/filebrowser/v2 CVE-2026-54093" on the vendor's site.
CVE-2026-54093 (github.com/filebrowser/filebrowser/v2) — CWE-22
Attack surface: filepath.ToSlash / ZipFile.ExtractToDirectory / nameOnDiskToNameInArchive / resourcePostHandler
Patched: 2.63.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in github.com/filebrowser/filebrowser/v2. Attackers reach the vulnerable code path via filepath.ToSlash.
Check the vendor advisory for the affected versions of github.com/filebrowser/filebrowser/v2. Attack surface: filepath.ToSlash / ZipFile.ExtractToDirectory / nameOnDiskToNameInArchive / resourcePostHandler.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 2.63.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/filebrowser/filebrowser/v2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/filebrowser/filebrowser/v2' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/filebrowser/filebrowser/v2を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/filebrowser/filebrowser/v2 to 2.63.6ステージング環境で 2.63.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com