CVE-2026-55667 File Browser: Out-of-scope file deletion by a Create-only scoped user via symlink-following RemoveAll in upload failure-cleanup
Authenticated users with create-only permissions can delete arbitrary files outside their scope via symlink exploitation during upload cleanup.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-55667?
CVE-2026-55667 is a high-severity path traversal vulnerability in filebrowser, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. Prior to 2.63.16, a scoped, non-admin File Browser user holding only the Create permission can delete arbitrary files outside their scope (other tenants' data, and the application's own database) via the upload failure-cleanup path. ScopedFs.RemoveAll is the one dereferencing operation that skips the symlink guard every other method enforces. The direct-upload handler runs RemoveAll on the user-controlled path during failed-upload cleanup, gated only by Perm.Create. If an escaping directory symlink already exists inside the user's scope, an authenticated create-only user can delete an out-of-scope target, bypassing both the ScopedFs boundary and the Perm.Delete gate. This vulnerability is fixed in 2.63.16.
Which versions are affected by CVE-2026-55667?
4 open source packages ship an affected version, including github.com/filebrowser/filebrowser/v2 and github.com/filebrowser/filebrowser.
| Package | Affected | Fixed in |
|---|---|---|
github.com/filebrowser/filebrowser/v2 Go | All versions | 2.63.16 |
github.com/filebrowser/filebrowser/v2 Go | All versions | 2.63.16 |
github.com/filebrowser/filebrowser/v2 Go | All versions | 2.63.16 |
github.com/filebrowser/filebrowser Go | All versions | None |
How do I fix CVE-2026-55667?
Upgrade github.com/filebrowser/filebrowser/v2 to 2.63.16 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-55667 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55667 exists.
Sources
Also known as GHSA-fmm7-x4gx-8jhr, GO-2026-6021.