filebrowser Allows Shell Commands to Spawn Other Commands

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.0 · CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H

EPSS

• CVE-2025-52903: 1.21% estimated exploitation activity in the next 30 days; percentile 68.35 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

[!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…

Published by the source

27 Jun 2025, 15:19 UTC

Last modified by the source

9 Jun 2026, 18:40 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3q2w-42mv-cph4

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-52903

Advisory: filebrowser Allows Shell Commands to Spawn Other Commands
IDs: CVE-2025-52903, GHSA-3q2w-42mv-cph4
Record: https://patchnext.com/advisories/cve-2025-52903 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/filebrowser/filebrowser/v2 2.33.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/filebrowser/filebrowser/v2: affected < 2.33.10; fixed in 2.33.10

## Suggested inspection (read-only)
- Go github.com/filebrowser/filebrowser/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/filebrowser/filebrowser/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3q2w-42mv-cph4 (GitHub-reviewed advisory GHSA-3q2w-42mv-cph4 lists affected ranges: Go github.com/filebrowser/filebrowser/v2 >=0 <2.33.10)

Commands are suggestions: review each one before running it.