FileBrowser Quantum's path traversal issue in subtitle handler allows any authenticated user to read arbitrary files
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-22 and the CVSS impact.
Summary
FileBrowser Quantum is a free, self-hosted, web-based file manager. Prior to version 1.4.3-beta, the `subtitlesHandler` endpoint (`GET /api/media/subtitles`) accepts two user-controlled query parameters: `path` and `name`, both of which are used in filesystem operations without sanitization, creating two independent path traversal vectors. The primary vector is the `path` parameter: it is passed directly to `idx.GetRealPath()` without calling `SanitizeUserPath()`, allowing an attacker to escape the storage root and set `parentDir` to any directory on the host. No existing anchor file is required. The secondary vector is the `name` parameter: it is joined with `parentDir` via `filepath.Join(parentDir, name)` without stripping directory components, allowing traversal relative to any resolved `parentDir`. Any authenticated user (regardless of role or permissions) can exploit either vector to read any text file readable by the server process, including `/etc/passwd`, SSH keys, database credentials, and JWT signing keys. Version 1.4.3-beta patches the issue.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| gtsteffaniak | filebrowser | before 1.4.3-beta | 1.4.3-beta | Patch available | CNA |
| — | github.com/gtsteffaniak/filebrowser/backend (Go) | before 0.0.0-20260608182036-f3f4bbe80cb5 | 0.0.0-20260608182036-f3f4bbe80cb5 | Patch available | GHSA-vvp7-h4fj-m28w |
- filebrowser Vendorgtsteffaniak Affected before 1.4.3-beta Fixed in 1.4.3-beta Patch available CNA
- github.com/gtsteffaniak/filebrowser/backend (Go) Vendor— Affected before 0.0.0-20260608182036-f3f4bbe80cb5 Fixed in 0.0.0-20260608182036-f3f4bbe80cb5 Patch available GHSA-vvp7-h4fj-m28w
Remediation
- Fix · CNA filebrowser (gtsteffaniak) Fixed in 1.4.3-beta
- Fix · GHSA-vvp7-h4fj-m28w github.com/gtsteffaniak/filebrowser/backend (Go) Fixed in 0.0.0-20260608182036-f3f4bbe80cb5 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2026-54910
- 2026-10-03 Alias added: GHSA-vvp7-h4fj-m28w
References
Other 5
- https://github.com/gtsteffaniak/filebrowser/security/advisories/GHSA-vvp7-h4fj-m28w
- https://github.com/gtsteffaniak/filebrowser/commit/f3f4bbe80cb569d664174aea874d7bfa008c3b5a
- https://github.com/gtsteffaniak/filebrowser/pull/2524
- https://github.com/gtsteffaniak/filebrowser
- https://github.com/gtsteffaniak/filebrowser/releases/tag/v1.4.3-beta
More gtsteffaniak vulnerabilities
- TI-2026-36047 FileBrowser Quantum: Path Traversal in public share PATCH allows file ops outside shared directory CVSS 4.0CRITICAL 9.3
- TI-2026-32454 FileBrowser Quantum: Unauthenticated Path Traversal in Public Share Delete Allows Arbitrary File Deletion CVSS 3.1CRITICAL 9.1
- TI-2026-81497 Symlink following in FileBrowser Quantum exposes out-of-scope files CVSS 3.1HIGH 8.6
- TI-2026-23759 FileBrowser Quantum: Stored XSS in public share page via unsanitized share metadata (text/template misuse) CVSS 3.1HIGH 8.9
- TI-2026-23758 FileBrowser Quantum Incomplete Remediation of CVE-2026-27611: Password-Protected Share Bypass via /public/api/share/info CVSS 3.1HIGH 7.5
- TI-2026-21997 FileBrowser Quantum: Password Protection Not Enforced on Shared File Links CVSS 4.0HIGH 7.1
Sources
- CVE-2026-54910 · CVE Program
- CVE-2026-54910 · NVD
- FIRST EPSS
- GHSA-vvp7-h4fj-m28w · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences