CVE-2025-52900: filebrowser Sets Insecure File Permissions
Summary ## The file access permissions for files uploaded to or created from File Browser are never explicitly set by the application. The same is true for the database used by File Browser. On standard servers where the umask configuration has not been hardened before, this makes all the stated files readable by any operating system account.
Published Jun 27, 2025 · Updated Aug 4, 2025
Affected packages
github.com/filebrowser/filebrowser/v2
- Ecosystem
- Go
- Affected
- < 2.33.7
- Fixed in
- 2.33.7
- Check
go list -m github.com/filebrowser/filebrowser/v2
github.com/filebrowser/filebrowser
- Ecosystem
- Go
- Affected
- <= 1.11.0
- Fixed in
- No patched version yet
- Check
go list -m github.com/filebrowser/filebrowser
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary ##
The file access permissions for files uploaded to or created from File Browser are never explicitly set by the application. The same is true for the database used by File Browser. On standard servers where the *umask* configuration has not been hardened before, this makes all the stated files readable by any operating system account.
Impact ##
The default permissions for new files on a standard Linux system are 0644, making them world-readable. That means that at least the following parties have full read access to all files managed by the Filebrowser from all *scopes*, as well as its database (including the password hashes stored in there):
- All OS accounts on the server
- All other applications running on the same server
- Any Filebrowser user with *Command Execution* privileges having access to a command that allows reading a file's content
Vulnerability Description ##
On a Linux system, the file access permissions of new files are designated by the system wide *umask* setting, unless they are configured manually. Most distributions set this value to 022 by default which gives every account on the system read permissions on the file.
$ umask
022
$ touch foo
$ ls -l foo
-rw-r--r-- 1 sba sba 0 31. Mär 15:08 fooProof of Concept ##
Upload or create a file in the Filebrowser GUI and list the directory contents from a shell:
$ ls -l /srv/filebrowser/testdir
total 12
-rw-r--r-- 1 sba sba 7703 Mar 25 16:07 dummy1.pdf
-rw-r--r-- 1 sba sba 3 Mar 25 15:46 testfile.txtThe same can be validated for Docker based deployments within the container:
$ docker exec -it e0f075082a2c ls /srv/testdir -l
total 12
-rw-r--r-- 1 1000 1000 7703 Mar 25 15:07 dummy1.pdf
-rw-r--r-- 1 1000 1000 3 Mar 25 14:46 testfile.txtFurthermore, the database used by the Filebrowser application is readable by any account:
$ ls -l /srv/filebrowser/filebrowser.db
-rw-rw-r-- 1 sba sba 65536 Mar 25 09:58 /srv/filebrowser/filebrowser.dbRecommended Countermeasures ##
Since the system's *umask* configuration cannot be controlled by the Filebrowser, the application needs to set the permissions of all new files manually upon creation. No permissions should be given to the *other* category.
Implementing this won't fix the permissions for active instances after an update, so site administrators will need to fix the permissions manually:
$ chmod o-rwx -R /srv/filebrowser/datadirTimeline ##
2025-03-25Identified the vulnerability in version 2.32.02025-04-11Contacted the project2025-04-18Vulnerability disclosed to the project2025-06-25Uploaded advisories to the project's GitHub repository2025-06-26CVE ID assigned by GitHub2025-06-26Fix released with version 2.33.7
References ##
- CWE-276: Incorrect Default Permissions
- What is Umask and How To Setup Default umask Under Linux?
- Original Advisory
Credits ##
- Mathias Tausig (SBA Research)
Credited to mtausig, hacdias.
References
- https://github.com/filebrowser/filebrowser/security/advisories/GHSA-jj2r-455p-5gvf
- https://nvd.nist.gov/vuln/detail/CVE-2025-52900
- https://github.com/filebrowser/filebrowser/commit/ca86f916216620365c0f81629c0934ce02574d76
- https://github.com/sbaresearch/advisories/tree/public/2025/SBA-ADV-20250325-03_Filebrowser_Insecure_File_Permissions
- https://pkg.go.dev/vuln/GO-2025-3785
- https://github.com/advisories/GHSA-jj2r-455p-5gvf
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-62683
File Browser: Trailing-slash directory deletion leaves public shares active for recreated paths
low3.1Nov 13, 2026CVE-2026-55667
File Browser: Out-of-scope file deletion by a Create-only scoped user via symlink-following RemoveAll in upload failure-cleanup
high8.2Jul 20, 2026CVE-2026-55668
File Browser: ScopedFs follows a dangling symlink on write, letting a scoped user create files outside their scope
medium6.3Jul 20, 2026CVE-2026-62684
File Browser: Share API exposes the password hash and bypass token
low2.7Jul 20, 2026CVE-2026-62685
File Browser: Colliding username normalization gives two users the same home directory
high8.1Jul 20, 2026CVE-2026-62843
File Browser: Archive builder turns backslash filenames into path traversal (zip-slip)
medium6.8Jul 20, 2026
