Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-54088 – Pre-Auth RCE via OS Command Injection – File Browser < 2.63.6

Be the first to know when new zero-days emerge:

Summary

CVE-2026-54088 is a critical pre-authentication OS command injection vulnerability in File Browser (filebrowser/filebrowser), a widely deployed open-source web-based file management interface. The flaw exists in the Hook Authentication feature, where user-supplied credentials are interpolated into shell command strings using os.Expand without any sanitization, allowing an unauthenticated remote attacker to execute arbitrary OS commands on the server before authentication takes place. This vulnerability carries a CVSS 4.0 score of 9.3 (Critical) and is fixed in version 2.63.6.

Technical details

  • Root cause: In auth/hook.go, the HookAuth.RunCommand function uses Go’s os.Expand() to interpolate the user-supplied username and password fields directly into the configured hook command string. No escaping, quoting, or input validation is applied prior to shell execution.
  • Trigger conditions: The Hook Authentication feature must be enabled by an administrator (non-default configuration). When enabled, any login attempt — including from unauthenticated users — passes credentials through the hook command, making the attack surface reachable with no prior access.
  • Attack vector: An unauthenticated remote attacker submits a crafted username or password containing shell metacharacters at the File Browser login screen. For example, if the configured command is sh -c "test $USERNAME = 'admin'", injecting ; id # as the username expands to sh -c "test ; id # = 'admin'", causing the injected command to execute with File Browser’s process privileges.
  • Impact: Full pre-authentication remote code execution (RCE). Successful exploitation yields complete compromise of confidentiality, integrity, and availability of the host system (CVSS VC:H/VI:H/VA:H). Attackers gain OS-level command execution as the user running the File Browser process.
  • Weaknesses: CWE-78 (OS Command Injection), CWE-88 (Argument Injection), CWE-306 (Missing Authentication for Critical Function).
  • Public PoC available: A proof-of-concept exploit repository was publicly indexed on June 12, 2026 (https://github.com/Saku0512/CVE-2026-54088-poc).

Affected software

  • File Browser all versions prior to 2.63.6 when the Hook Authentication feature is enabled.

Severity

  • CVSS 4.0 Base Score: 9.3 (Critical)
  • CVSS 4.0 Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate — Patch: Upgrade File Browser to version 2.63.6 or later, which addresses this vulnerability.
  • If immediate patching is not possible — Workaround: Disable the Hook Authentication feature. Removing the hook command configuration eliminates the vulnerable code path entirely, reducing exposure until an upgrade can be performed.
  • Network mitigation: Restrict internet-facing access to File Browser instances. Ensure that any deployment not requiring external access is placed behind a firewall or network access controls to limit the reachable attack surface.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge