Vulnerability · Published Sep 14, 2026 · Assigned by VulnCheck
CVE-2026-90929File Browser 2.5.0 Directory Deletion via Upload Failure Cleanup
High 8.1
In plain English
A high-severity incorrect authorization in filebrowser from filebrowser. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 38% of all known vulnerabilities).
Official description
File Browser versions >= 2.5.0 and <= 2.63.23 contain an incorrect authorization flaw in the direct-upload endpoint (resourcePostHandler in http/resource.go). Unlike the TUS upload handler, the direct-upload handler does not reject a target that is an existing directory; a POST with ?override=true aimed at a directory fails inside writeFile (a directory cannot be opened for writing) and the failure-cleanup path then calls Fs.RemoveAll on the request path, recursively deleting the entire tree. This cleanup is gated by neither the Perm.Delete permission nor the checkDescendants rule walk applied by the delete and patch handlers, so an authenticated non-administrator holding only the default Create and Modify permissions can delete directories they are not authorized to delete, including rule-denied files within them. Deletion remains confined to the user's scope because ScopedFs.RemoveAll still enforces the scope guard. The faulty cleanup was introduced in v2.5.0; no patched version is available.
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| filebrowser | filebrowser | 2.5.0 – through 2.63.23 |
Weakness: CWE-863 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
References
- GitHub Security Advisory (GHSA-c4fr-5f24-4wrj) vendor-advisory
- VulnCheck Advisory: File Browser 2.5.0 Directory Deletion via Upload Failure Cleanup third-party-advisory