CVE-2026-72836
FileBrowser before 2.63.19 does not account for case-insensitive filesystems when checking home directory ownership during self-registration.
Impact
FileBrowser before 2.63.19 does not account for case-insensitive filesystems when checking home directory ownership during self-registration. When Signup and CreateUserDir are enabled and FileBrowser's root is on a case-insensitive filesystem (confirmed on Windows/NTFS), two self-registered usernames that differ only in letter case (e.g., CaseVictim and casevictim) are stored as distinct accounts but resolve to the same physical home directory, because the scope-ownership check compares the persisted scope as an exact case-sensitive string. A second registrant can therefore read, overwrite, and delete another account's files through authenticated HTTP endpoints, without needing an existing account or victim interaction.
Affected products
| Product | Affected versions |
|---|---|
| FileBrowser | before 2.63.19 |
Versions were read from the advisory text. No structured product data has been published for this record yet.
Weakness classification
References
- NVD record
- CVE.org record
- https://github.com/filebrowser/filebrowser/commit/fe7efb2e6afe66774cd86a5b0a03033bd514d0c0
- https://github.com/filebrowser/filebrowser/security/advisories/GHSA-576v-w77m-gr84
- https://www.vulncheck.com/advisories/filebrowser-before-case-sensitivity-authentication-bypass
- https://github.com/filebrowser/filebrowser/security/advisories/GHSA-576v-w77m-gr84