Vulnerability in github.com/filebrowser/filebrowser/v2 (CVE-2026-54096)
Summary
Vulnerability in github.com/filebrowser/filebrowser/v2 (CVE-2026-54096). Successful exploitation can lead to full system takeover. Exploitable via POST /api/share/. Mitigation: upgrade to 2.63.7 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.7, POST /api/share/ accepts an authenticated request for an arbitrary path and stores a public share record without checking whether the target file currently exists. Later, when a file is created at that same path, the previously created public share immediately becomes valid and exposes the new file through GET /api/public/dl/. This vulnerability is fixed in 2.63.7.
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-54096 has been found in github.com/filebrowser/filebrowser/v2.
Attackers can target a specific entry point like POST /api/share/ over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.4/10.
What to do: upgrade github.com/filebrowser/filebrowser/v2 to 2.63.7 or later.
If unsure, ask your IT team or search "github.com/filebrowser/filebrowser/v2 CVE-2026-54096" on the vendor's site.
CVE-2026-54096 (github.com/filebrowser/filebrowser/v2) — CWE-367 / CVSS v3 8.4
Attack vector: local / unauthenticated / no user interaction
Attack surface: POST /api/share/ / GET /api/public/dl/ / GET /api/public/share/ / MediaProvider
Patched: 2.63.7 — 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.
A vulnerability (CWE-367) exists in github.com/filebrowser/filebrowser/v2. Attackers reach the vulnerable code path via POST /api/share/ without authentication.
Check the vendor advisory for the affected versions of github.com/filebrowser/filebrowser/v2. Attack surface: POST /api/share/ / GET /api/public/dl/ / GET /api/public/share/ / MediaProvider.
Severity: High (CVSS 8.4/10). Successful exploitation can lead to full system takeover.
Update to 2.63.7.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /api/share/ requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/share/' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/share/への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/filebrowser/filebrowser/v2 to 2.63.7ステージング環境で 2.63.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/share/ 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
- web github.com