CVE-2026-54094: File Browser symlink following scope bypass

CVE-2026-54094 · Severity: high · CVSS 7.5 · Published 2026-06-25

File Browser, a web-based file management interface, contains a security flaw that allows users to access files outside of their assigned folders. By using symbolic links (shortcuts), a restricted user or even an unauthenticated person with a shared link can bypass security boundaries to read or overwrite sensitive system files. This could lead to the exposure of private data or the corruption of critical files on the server hosting the application.

Technologies: File Browser, github.com/filebrowser/filebrowser (Go), github.com/filebrowser/filebrowser/v2 (Go). Vendors: File Browser, Go.

Quick answers

Is CVE-2026-54094 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-54094 being exploited in the wild.
How severe is CVE-2026-54094?
High severity, with a CVSS score of 7.5, published 25 June 2026.
Which products and versions are affected?
File Browser < 2.63.14; github.com/filebrowser/filebrowser (Go) <= 1.11.0, SEMVER:introduced=0, SEMVER:introduced=0,last_affected=1.11.0; github.com/filebrowser/filebrowser/v2 (Go) <= 2.63.13, SEMVER:introduced=0,fixed=2.63.14.
Is there a fix for CVE-2026-54094?
Yes. github.com/filebrowser/filebrowser/v2 (Go): upgrade to 2.63.14 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-54094 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-54094?
Check whether you run File Browser, github.com/filebrowser/filebrowser (Go) or github.com/filebrowser/filebrowser/v2 (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/filebrowser/filebrowser/v2 (Go): upgrade to 2.63.14 or later
    go get github.com/filebrowser/filebrowser/v2@v2.63.14

Technical details

File Browser uses 'afero.NewBasePathFs' to enforce user scopes, which prevents lexical path traversal (e.g., using '../') but does not stop the underlying filesystem from resolving symbolic links. The vulnerability manifests in two variants: direct symlinks to out-of-scope files and files accessed through a symlinked parent directory. Because the application's metadata layer and HTTP handlers (including raw, resource, TUS upload, and share handlers) do not consistently validate the resolved target path against the user's scope, attackers can perform unauthorized read and write operations. This affects various API endpoints such as /api/raw/, /api/resources/, and /api/tus/. The issue is resolved in version 2.63.14.

Affected products

  • filebrowser File Browser < 2.63.14

Identifiers

  • CVE-2026-54094
  • GHSA-239w-m3h6-ch8v
  • GO-2026-5055

Timeline

  • 2026-06-03: advisory: GitHub security advisory published
  • 2026-06-25: disclosed: NVD publication date
  • 2026-06-25: patched: Fix confirmed in version 2.63.14

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.