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

Back
New CVE Detected

CVE-2026-82235 – Denial of Service via Named Pipe Archive Downloads – File Browser ≤ 2.63.23

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-82235 is a Denial of Service vulnerability (CWE-400: Uncontrolled Resource Consumption) affecting File Browser (the filebrowser/filebrowser Go project), through version 2.63.23. The application fails to validate named pipes before opening them in its directory archive and public download handlers, allowing an attacker to trigger blocking open syscalls and exhaust server resources. The flaw carries a CVSS v4.0 base score of 8.2 (High) and is exploitable remotely without authentication against public share links.

Technical details

  • Root cause: File Browser’s archive-creation and public download/raw-file handlers open requested files without checking whether they are named pipes (FIFOs) rather than regular files.
  • Trigger: An attacker places or references a named pipe within a directory the server can access, then repeatedly requests an archive or public download that includes it.
  • Attack vector: Network — exploitable both by authenticated users and by anonymous visitors using a public share link, requiring no user interaction.
  • Impact: Each request causes a blocking open syscall on the pipe, pinning a server goroutine indefinitely; repeated requests exhaust available goroutines/connections, leading to denial of service for legitimate users. No confidentiality or integrity impact is reported.

Affected software

  • filebrowser/filebrowser (Go module github.com/filebrowser/filebrowser/v2) — all versions through 2.63.23.

Severity

  • CVSS v4.0: 8.2 (High) — CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
  • CVSS v3.1: 5.9 (Medium) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Mitigation and recommended actions

  • No patched release is available: the File Browser project has ended active development, with version 2.63.23 confirmed as its final release and the repository scheduled for archival; no further bug or security fixes will be issued.
  • Do not expose File Browser instances to the public Internet; restrict access to trusted internal networks or place it behind an authenticating reverse proxy/VPN.
  • Disable or restrict public share links and directory archive/download functionality where not strictly required.
  • Audit and remove any named pipes (FIFOs) from directories served by File Browser, and prevent users from being able to create them within managed shares.
  • Monitor server resource usage (goroutine counts, open connections) for signs of exhaustion, and consider request-rate limiting on archive/download endpoints.
  • Given the project is unmaintained, evaluate migrating to an actively maintained alternative file-management solution.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge