File Browser vulnerable to command execution allowlist bypass

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-52995: 0.64% estimated exploitation activity in the next 30 days; percentile 50.51 (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.

Summary

The Command Execution feature of Filebrowser only allows the execution of shell command which have been predefined on a user-specific allowlist. The implementation of this allowlist is erroneous, allowing a user to execute additional commands not permitted. Impact

A user can execute more shell commands than they are authorized for. The concrete impact of this vulnerability depends on the commands configured, and the binaries installed on the server or in the container image. Due to the missing separation of scopes on the OS-level, this could give an attacker access to all files managed the application, including the File Browser database. Vulnerability Description

For a user to make use of the command execution feature, two things need to happen in advance: 1. An administrator needs to grant that account the Execute commands permission 2. The command to be executed needs to be listed in the Commands input field (also done by an administrator) If a user tries to…

Published by the source

30 Jun 2025, 17:46 UTC

Last modified by the source

4 Aug 2025, 20:32 UTC

Source last checked

26 Oct 2026, 15:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-w7qc-6grj-w7r8

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

# Patch Next advisory brief: CVE-2025-52995

Advisory: File Browser vulnerable to command execution allowlist bypass
IDs: CVE-2025-52995, GHSA-w7qc-6grj-w7r8
Record: https://patchnext.com/advisories/cve-2025-52995 (revision 1, source checked 26 Oct 2026, 15:10 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: Partial vendor fix; 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
- Go github.com/filebrowser/filebrowser: affected <= 1.11.0

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/filebrowser/filebrowser/v2, github.com/filebrowser/filebrowser.
- 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-w7qc-6grj-w7r8 (GitHub-reviewed advisory GHSA-w7qc-6grj-w7r8 lists affected ranges: Go github.com/filebrowser/filebrowser/v2 >=0 =0 <=1.11.0)

Commands are suggestions: review each one before running it.