/

CVE-2026-54094

Severity:

HIGH RISK

(7.5)

Path Traversal via Symlinks (CWE-22) in File Browser

CVE-2026-54094

Deferred

Vulnerability type

Category:

Path Traversal / Symlink Following

CWE:

CWE-22, CWE-59

Impact:

Unauthorized File System Access

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

File Browser prior to version 2.63.14 allows HTTP file handlers to follow symbolic links without verifying that their targets remain within the user's scoped directory.

Under these conditions, a scoped user or public-share recipient can access files outside the intended scope, potentially exposing sensitive data or enabling unintended file operations.

Affected context

This vulnerability appears in deployments of File Browser where users are restricted to specific directory scopes or where public shares expose a subset of files.

It becomes relevant when the application allows creation or use of symbolic links that lexically reside within the allowed scope but point to file system locations beyond that scope. This behavior affects operations such as opening, serving, writing, sharing, or listing files through the HTTP interface.

Exploit preconditions

  • Attack surface: HTTP file management endpoints (open, serve, write, share, list) exposed by File Browser.
  • Required access: A scoped user account or access to a public share that permits interaction with files, including symlinked entries.
  • Trigger point: Performing file operations on a symbolic link whose path exists within the assigned scope, but whose target points outside that scope.
  • Why exploitation is possible: The application enforces scope boundaries only based on the lexical path of the requested resource and does not re-check the resolved symlink target against the configured scope before performing file operations.

Why this happens

The underlying issue is a lack of proper canonicalization and validation of file paths before performing operations, combined with unrestricted symbolic link resolution.

Conceptually, this maps to CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') and CWE-59: Improper Link Resolution Before File Access ('Link Following'). The software assumes that a file path inside the scoped directory is safe, but it does not account for symlinks that redirect operations to locations outside the intended scope, allowing users to bypass directory restrictions.

Potential impact

  • Access to files outside the user's assigned directory scope that may contain sensitive information.
  • Reading configuration or data files belonging to other users or system components.
  • Overwriting or modifying files outside the scoped directory that the File Browser process has permission to change.
  • Expanding a public share's effective reach to unintended directories via symlink traversal.
  • Facilitating information disclosure that could support further attacks against the hosting environment.

General mitigation guidance

Effective mitigation focuses on enforcing directory scope after resolving symbolic links and other indirections.

Common defensive patterns include:

  • Resolving paths to a canonical form (e.g., following symlinks, removing . and ..) and verifying that the final target resides within the configured scope before any file operation.
  • Denying or restricting symlink usage in scoped or shared directories where strict boundaries are required.
  • Applying least-privilege to the file management process so that even if a boundary check fails, the process can access only minimally necessary locations.
  • Implementing a clear trust boundary for user-controlled paths and performing robust validation before opening, serving, writing, sharing, or listing files.

How teams detect issues like this

Organizations can detect similar issues by:

  • Using static analysis rules that flag direct file operations on user-supplied paths without canonicalization or scope checks.
  • Reviewing code for patterns where open, stat, readdir, or similar APIs are called using paths derived from HTTP parameters or user input, especially when symlinks are permitted.
  • Establishing security review checklists that require explicit mention of symlink handling and directory boundary enforcement in file management components.
  • Employing file-system level monitoring or audit logs to identify access to paths outside intended scopes initiated by web-facing services.

Sources

SourceLink
github.comgithub.com/filebrowser/filebrowser/security/advisories/GHSA-239w-m3h6-ch8v

Frequently asked

questions

It is exploitable wherever scoped directories or public shares are used and symbolic links can exist within those scopes. Any user or share recipient who can interact with symlinked entries may be able to reach files outside the intended boundary.

Typically, a scoped user account in File Browser or access to a public share that exposes symlinked content is required. The actual impact is limited by the file system permissions granted to the File Browser process.

The safest approach is to canonicalize the target path after resolving symlinks and verify that it remains within the configured scope before performing any file operation. Optionally, disallow symlinks in scoped or shared directories when strict isolation is needed.

Treat all paths derived from user input as untrusted, perform robust canonicalization, and enforce directory boundaries using the resolved path rather than the lexical path. Combine this with least-privilege execution for file-handling services and explicit policies for symlink handling.

Find out what's already
exploitable in your codebase.