File Browser allows sensitive data to be transferred in URL

Exploitation

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

CVSS

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

EPSS

• CVE-2025-52901: 0.54% estimated exploitation activity in the next 30 days; percentile 45.37 (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 URLs that are accessed by a user are commonly logged in many locations, both server- and client-side. It is thus good practice to never transmit any secret information as part of a URL. The Filebrowser violates this practice, since access tokens are used as GET parameters. Impact The JSON Web Token (JWT) which is used as a session identifier will get leaked to anyone having access to the URLs accessed by the user. This will give the attacker full access to the user's account and, in consequence, to all sensitive files the user has access to. Description Sensitive information in URLs is logged by several components (see the following examples), even if access is protected by TLS. The browser history The access logs on the affected web server Proxy servers or reverse proxy servers Third-party servers via the HTTP referrer header In case attackers can access certain logs, they could read the included sensitive data. Proof of Concept

When a file is downloaded via the web…

Published by the source

30 Jun 2025, 17:44 UTC

Last modified by the source

4 Aug 2025, 17:22 UTC

Source last checked

26 Oct 2026, 15:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rmwh-g367-mj4x

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

# Patch Next advisory brief: CVE-2025-52901

Advisory: File Browser allows sensitive data to be transferred in URL
IDs: CVE-2025-52901, GHSA-rmwh-g367-mj4x
Record: https://patchnext.com/advisories/cve-2025-52901 (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 4.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.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/filebrowser/filebrowser/v2: affected < 2.33.9; fixed in 2.33.9
- 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-rmwh-g367-mj4x (GitHub-reviewed advisory GHSA-rmwh-g367-mj4x lists affected ranges: Go github.com/filebrowser/filebrowser/v2 >=0 =0 <=1.11.0)

Commands are suggestions: review each one before running it.