CVE-2026-72836: FileBrowser before 2.63.19 Case Sensitivity Authentication Bypass
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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
FileBrowserto a version that resolves this vulnerability.Fixed in 2.63.19 - Configuration
If you cannot immediately upgrade, disable self-registration features (set Signup and CreateUserDir to disabled) to prevent exploiting authenticated HTTP endpoints and the self-registration case-sensitivity authentication bypass on case-insensitive filesystems.
FileBrowser Signup and CreateUserDir = disabled
Event History
Frequently Asked Questions
What is the severity of CVE-2026-72836?
The severity of CVE-2026-72836 is classified as high, with a score of 8.1.
How do I fix CVE-2026-72836?
To fix CVE-2026-72836, upgrade FileBrowser to version 2.63.19 or later.
What systems are affected by CVE-2026-72836?
CVE-2026-72836 affects FileBrowser versions before 2.63.19 running on case-insensitive filesystems.
What does CVE-2026-72836 exploit?
CVE-2026-72836 exploits a case sensitivity issue that allows bypassing authentication during self-registration.
Is user data at risk with CVE-2026-72836?
Yes, CVE-2026-72836 may risk user data since it can allow unauthorized users to access home directories.