File Browser vulnerable to insecure password handling

Exploitation

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

CVSS

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

EPSS

• CVE-2025-52997: 0.54% estimated exploitation activity in the next 30 days; percentile 45.48 (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

All user accounts authenticate towards a File Browser instance with a password. A missing password policy and brute-force protection makes it impossible for administrators to properly secure the authentication process. Impact

Attackers can mount a brute-force attack against the passwords of all accounts of an instance. Since the application is lacking the ability to prevent users from choosing a weak password, the attack is likely to succeed. Vulnerability Description

The application implement a classical authentication scheme using a username and password combination. While employed by many systems, this scheme is quite error-prone and a common cause for vulnerabilities. File Browser's implementation has multiple weak points: 1. Since the application is missing the capability for administrators to define a password policy, users are at liberty to set trivial and well-known passwords such as secret or even ones with only single digit like 1. 2. New instances are set…

Published by the source

30 Jun 2025, 17:50 UTC

Last modified by the source

4 Aug 2025, 17:39 UTC

Source last checked

26 Oct 2026, 15:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cm2r-rg7r-p7gg

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

# Patch Next advisory brief: CVE-2025-52997

Advisory: File Browser vulnerable to insecure password handling
IDs: CVE-2025-52997, GHSA-cm2r-rg7r-p7gg
Record: https://patchnext.com/advisories/cve-2025-52997 (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: Medium (CVSS 5.9)
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.34.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/filebrowser/filebrowser/v2: affected <= 2.34.0; fixed in 2.34.1
- 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-cm2r-rg7r-p7gg (GitHub-reviewed advisory GHSA-cm2r-rg7r-p7gg lists affected ranges: Go github.com/filebrowser/filebrowser/v2 >=0 =0 <=1.11.0)

Commands are suggestions: review each one before running it.