External risk intelligence

Filebrowser Unrestricted File Access via Self-Signup Privilege Escalation.

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-72839

Filebrowser is a web-based file management application typically deployed as a public-facing service. The vulnerability exists within the self-signup and account management functionality, which is a feature inherently designed to be accessible to users over the network.

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory describes a critical vulnerability in the file management tool Filebrowser that could allow unauthenticated attackers to gain unrestricted access to all files on a server if self-signup is enabled with default settings. The issue stems from improper scope and permission restrictions, enabling attackers to create accounts with server-wide administrative privileges.

  • Unauthenticated users can gain full server file access.
  • Confirms broad, unauthorized server access potential.
  • Verify if self-signup is enabled and review permissions.

Attack Path

How an attacker could exploit the issue

Unauthenticated attackers can exploit this vulnerability by registering an account on a Filebrowser instance where self-signup is enabled. This allows them to create user accounts that inherit the server's root directory scope, granting them full permissions to create, modify, delete, rename, share, and download any file on the server.

  • Entry condition: Self-signup is enabled.
  • Trigger point: Registering a new user account.
  • Resulting risk: Unrestricted access to all server files.

Live Threat

Current exploitation, exposure, and threat context

When self-signup is enabled with default settings, unauthenticated attackers could register accounts that gain unrestricted access to all files on the server.

  • Server files could be exposed.
  • Unauthenticated users could register accounts.
  • Unrestricted access to all files.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts Filebrowser instances with self-signup enabled. Owners of Filebrowser deployments, likely within application or infrastructure teams, must identify affected systems, confirm their exposure and criticality, and then plan remediation. Coordination with any vendor providing Filebrowser as a service will also be necessary.

  • Determine accountable Filebrowser owners.
  • Verify self-signup enabled and network exposure.
  • Plan remediation based on asset criticality.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Filebrowser and how is it used?

Filebrowser is a web-based file management application that provides a graphical interface for interacting with files on a server. It is commonly deployed to allow users to remotely upload, download, edit, and organize files via a browser, effectively turning a directory tree into a user-friendly management portal.

What does CWE-266 mean for CVE-2026-72839?

CWE-266 identifies an Incorrect Privilege Assignment. In the context of this CVE, the software fails to properly constrain the permissions granted to newly registered users. Instead of receiving limited, restricted access, a new account created during self-signup erroneously inherits administrative-level authority over the entire file system.

How can an attacker trigger this vulnerability?

An attacker triggers this by navigating to a Filebrowser instance where self-signup is enabled and simply registering a new account. This bug is specifically tied to the default CreateUserDir setting; it does not trigger if self-signup is disabled or if the application is configured to restrict user directories to a specific, isolated path.

Is my Filebrowser instance at risk?

Halo Surface Signal notes that Filebrowser is frequently deployed as a public-facing service, which significantly increases risk if self-signup is enabled. If your instance is accessible over the internet and allows arbitrary user registration, it is highly susceptible to this privilege escalation issue regardless of the user's intended role.

What should I do to protect my server?

Immediately verify if self-signup is enabled in your Filebrowser configuration. If it is, disable the feature to prevent unauthorized account creation until you can apply the necessary updates or security patches provided by the project maintainers. Review all existing user accounts to ensure no unauthorized administrative users were added while the service was exposed.

References