Path Traversal in github.com/gtsteffaniak/filebrowser (CVE-2026-44542)
Summary
Path traversal in github.com/gtsteffaniak/filebrowser (CVE-2026-44542). Data can be tampered with by attackers. Exploitable via DELETE /public/api/resources. Mitigation: upgrade to 0.0.0-20260501183844-112740bdd41d or later.
Original description
The description as published by the source.
FileBrowser Quantum is a free, self-hosted, web-based file manager. Prior to 1.3.1-stable and 1.3.9-beta, attacker-controlled path input is joined with a trusted base path prior to sanitization, allowing traversal sequences (e.g., ../) to escape the intended shared directory. As a result, an unauthenticated attacker possessing a valid public share hash with delete permissions enabled can delete arbitrary files outside the shared directory within the share owner’s configured storage scope. This affects public/api/resources and public/api/resources/bulk. This vulnerability is fixed in 1.3.1-stable and 1.3.9-beta.
Source: NIST National Vulnerability Database 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-44542 has been found in github.com/gtsteffaniak/filebrowser.
Attackers can target a specific entry point like DELETE /public/api/resources over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 9.1/10.
What to do: upgrade github.com/gtsteffaniak/filebrowser to 0.0.0-20260501183844-112740bdd41d or later.
If unsure, ask your IT team or search "github.com/gtsteffaniak/filebrowser CVE-2026-44542" on the vendor's site.
CVE-2026-44542 (github.com/gtsteffaniak/filebrowser) — CWE-22 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: DELETE /public/api/resources / DELETE /public/api/resources/bulk
Patched: 0.0.0-20260501183844-112740bdd41d — 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/gtsteffaniak/filebrowser. Attackers reach the vulnerable code path via DELETE /public/api/resources without authentication.
Check the vendor advisory for the affected versions of github.com/gtsteffaniak/filebrowser. Attack surface: DELETE /public/api/resources / DELETE /public/api/resources/bulk.
Severity: Critical (CVSS 9.1/10). Data can be tampered with by attackers.
Update to 0.0.0-20260501183844-112740bdd41d.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual DELETE /public/api/resources requests with malformed payloads or SQL meta-characters. Run grep -r 'github.com/gtsteffaniak/filebrowser' . 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/gtsteffaniak/filebrowser' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/gtsteffaniak/filebrowserを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'DELETE /public/api/resources' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
DELETE /public/api/resourcesへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/gtsteffaniak/filebrowser to 0.0.0-20260501183844-112740bdd41dステージング環境で 0.0.0-20260501183844-112740bdd41d に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against DELETE /public/api/resources on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com