# CVE-2026-54910: FileBrowser Quantum's path traversal issue in subtitle handler allows any authenticated user to read arbitrary files

> Authenticated users can read arbitrary files on the server via path traversal in the subtitle handler, exposing sensitive data like credentials and keys.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-vvp7-h4fj-m28w, GO-2026-6164

## What is CVE-2026-54910?

CVE-2026-54910 is a high-severity path traversal vulnerability in gtsteffaniak filebrowser, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-23 (Relative Path Traversal), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-54910?

3 open source packages ship an affected version, including github.com/gtsteffaniak/filebrowser/backend.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/gtsteffaniak/filebrowser/backend` | Go | All versions | 0.0.0-20260608182036-f3f4bbe80cb5 |
| `github.com/gtsteffaniak/filebrowser/backend` | Go | All versions | 0.0.0-20260608182036-f3f4bbe80cb5 |
| `github.com/gtsteffaniak/filebrowser/backend` | Go | All versions | 0.0.0-20260608182036-f3f4bbe80cb5 |

## How do I fix CVE-2026-54910?

Upgrade github.com/gtsteffaniak/filebrowser/backend to 0.0.0-20260608182036-f3f4bbe80cb5 or later.

## Is CVE-2026-54910 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54910 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54910 and fix it if it is affected.

What it is: CVE-2026-54910 is a high-severity path traversal vulnerability in gtsteffaniak filebrowser, published on 20 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54910 exists.

Affected packages and fixed versions:
- github.com/gtsteffaniak/filebrowser/backend (Go): affected all versions; fixed in 0.0.0-20260608182036-f3f4bbe80cb5
- github.com/gtsteffaniak/filebrowser/backend (Go): affected all versions; fixed in 0.0.0-20260608182036-f3f4bbe80cb5
- github.com/gtsteffaniak/filebrowser/backend (Go): affected all versions; fixed in 0.0.0-20260608182036-f3f4bbe80cb5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54910/ (Markdown: https://insights.sbomify.com/CVE-2026-54910/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54910
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54910
- OSV: https://osv.dev/vulnerability/CVE-2026-54910

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54910/
Summaries are generated and may contain mistakes; the official description above is the record.