File Browser has an Authentication Bypass in User Password Update

Exploitation

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

CVSS

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

EPSS

• CVE-2026-25889: 0.37% estimated exploitation activity in the next 30 days; percentile 30.54 (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.

Security Advisory: Authentication Bypass in User Password Update Summary A case-sensitivity flaw in the password validation logic allows any authenticated user to change their password (or an admin to change any user's password) without providing the current password. By using Title Case field name "Password" instead of lowercase "password" in the API request, the currentpassword verification is completely bypassed. This enables account takeover if an attacker obtains a valid JWT token through XSS, session hijacking, or other means. CVSS Score: 7.5 (High) CWE: CWE-178 (Improper Handling of Case Sensitivity) --- Details The vulnerability exists in http/users.go in the userPutHandler function (lines 181-200). Vulnerable Code Root Cause 1. The sensibleFields map uses lowercase keys (e.g., "password") 2. The lookup sensibleFields[field] is case-sensitive 3. When req.Which contains "Password" (Title Case), the lookup returns false 4. The password verification block is skipped entirely 5.…

Published by the source

10 Feb 2026, 00:22 UTC

Last modified by the source

10 Feb 2026, 02:56 UTC

Source last checked

26 Oct 2026, 15:14 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-hxw8-4h9j-hq2r

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

# Patch Next advisory brief: CVE-2026-25889

Advisory: File Browser has an Authentication Bypass in User Password Update
IDs: CVE-2026-25889, GHSA-hxw8-4h9j-hq2r
Record: https://patchnext.com/advisories/cve-2026-25889 (revision 1, source checked 26 Oct 2026, 15:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
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.57.1. A vendor fix does not mean a deployment is fixed.

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

## 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-hxw8-4h9j-hq2r (GitHub-reviewed advisory GHSA-hxw8-4h9j-hq2r lists affected ranges: Go github.com/filebrowser/filebrowser/v2 >=0 <=2.57.0)

Commands are suggestions: review each one before running it.