CVE-2026-90929

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.

Predictions

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

References

• https://github.com/filebrowser/filebrowser/security/advisories/GHSA-c4fr-5f24-4wrj
• https://www.vulncheck.com/advisories/file-browser-2.5.0-directory-deletion-via-upload-failure-cleanup

CWEs

CWE-863