filebrowser Sets Insecure File Permissions

Exploitation

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

CVSS

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

EPSS

• CVE-2025-52900: 0.22% estimated exploitation activity in the next 30 days; percentile 12.89 (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 file access permissions for files uploaded to or created from File Browser are never explicitly set by the application. The same is true for the database used by File Browser. On standard servers where the umask configuration has not been hardened before, this makes all the stated files readable by any operating system account. Impact

The default permissions for new files on a standard Linux system are 0644, making them world-readable. That means that at least the following parties have full read access to all files managed by the Filebrowser from all scopes, as well as its database (including the password hashes stored in there): All OS accounts on the server All other applications running on the same server Any Filebrowser user with Command Execution privileges having access to a command that allows reading a file's content Vulnerability Description

On a Linux system, the file access permissions of new files are designated by the system wide umask setting,…

Published by the source

27 Jun 2025, 14:55 UTC

Last modified by the source

4 Aug 2025, 20:31 UTC

Source last checked

26 Oct 2026, 15:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jj2r-455p-5gvf

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

# Patch Next advisory brief: CVE-2025-52900

Advisory: filebrowser Sets Insecure File Permissions
IDs: CVE-2025-52900, GHSA-jj2r-455p-5gvf
Record: https://patchnext.com/advisories/cve-2025-52900 (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.5)
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.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/filebrowser/filebrowser/v2: affected < 2.33.7; fixed in 2.33.7
- 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-jj2r-455p-5gvf (GitHub-reviewed advisory GHSA-jj2r-455p-5gvf lists affected ranges: Go github.com/filebrowser/filebrowser/v2 >=0 =0 <=1.11.0)

Commands are suggestions: review each one before running it.