Is CVE-2026-82235 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-82235 being exploited in the wild.

How severe is CVE-2026-82235?

Medium severity, with a CVSS score of 5.9, published 28 August 2026.

Is there a fix for CVE-2026-82235?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-82235 attacked?

It is attacked over the network.

Am I affected by CVE-2026-82235?

Check whether you run Filebrowser at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-82235: filebrowser named pipe blocking in archive and public download handlers

CVE-2026-82235 · Severity: medium · CVSS 5.9 · Published 2026-08-28

filebrowser is a web-based file manager used to browse and download files from servers. When archiving directories or downloading files via public share links, the application fails to block named pipes (special files used for inter-process communication). An attacker can craft requests involving these special files to cause the server to hang indefinitely, pinning server resources and eventually denying service to legitimate users through resource exhaustion.

Technologies: Filebrowser. Vendors: FileBrowser.

Quick answers

Is CVE-2026-82235 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-82235 being exploited in the wild.
How severe is CVE-2026-82235?: Medium severity, with a CVSS score of 5.9, published 28 August 2026.
Which products and versions are affected?: Filebrowser through 2.63.23.
Is there a fix for CVE-2026-82235?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-82235 attacked?: It is attacked over the network.
Am I affected by CVE-2026-82235?: Check whether you run Filebrowser at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability is a resource exhaustion / denial-of-service issue in filebrowser's archive and public download handlers. The root cause is inconsistent validation of named pipes: while the single-file download handler (rawHandler) includes a guard to reject named pipes, the directory archive walker (getFiles) and public download handler (publicDlHandler) do not. When these handlers attempt to open a named pipe without a writer attached, the open(2) syscall blocks indefinitely. Because context cancellation cannot interrupt a blocking open syscall, the request goroutine and client connection remain pinned with no timeout mechanism to recover. Authenticated users can trigger this via the archive API endpoint, and anonymous visitors can trigger it via public share links pointing to directories containing or directly to a named pipe. Repeated requests accumulate pinned goroutines, degrading server availability. The project is no longer maintained and no patch will be released.

Affected products

filebrowser filebrowser through 2.63.23

Timeline

2026-08-14: disclosed
2026-08-28: advisory
other: Project archived and no longer maintained; no patch will be released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.