# CVE-2026-32760: File Browser Self Registration Grants Any User Admin Access When Default Permissions Include Admin > Unauthenticated users can gain admin privileges if self-registration is enabled with admin permissions in defaults, allowing full system control. - **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 Mar 2026 - **Updated:** 25 Mar 2026 - **Also known as:** GHSA-5gg9-5g7w-hm73, GO-2026-4710 ## What is CVE-2026-32760? CVE-2026-32760 is a critical vulnerability in filebrowser, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, 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. In versions 2.61.2 and below, any unauthenticated visitor can register a full administrator account when self-registration (signup = true) is enabled and the default user permissions have perm.admin = true. The signup handler blindly applies all default settings (including Perm.Admin) to the new user without any server-side guard that strips admin from self-registered accounts. The signupHandler is supposed to create unprivileged accounts for new visitors. It contains no explicit user.Perm.Admin = false reset after applying defaults. If an administrator (intentionally or accidentally) configures defaults.perm.admin = true and also enables signup, every account created via the public registration endpoint is an administrator with full control over all files, users, and server settings. This issue has been resolved in version 2.62.0. Weakness: CWE-284 (Improper Access Control), CWE-269 (Improper Privilege Management) ## Which versions are affected by CVE-2026-32760? 4 open source packages ship an affected version, including github.com/filebrowser/filebrowser/v2 and github.com/filebrowser/filebrowser. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.62.0 | | `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.62.0 | | `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.62.0 | | `github.com/filebrowser/filebrowser` | Go | All versions | None | Products: Filebrowser Filebrowser. ## How do I fix CVE-2026-32760? Upgrade github.com/filebrowser/filebrowser/v2 to 2.62.0 or later. ## Is CVE-2026-32760 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32760 exists. ## Other vulnerabilities in filebrowser - [CVE-2026-29188](https://insights.sbomify.com/CVE-2026-29188/): File Browser: TUS Delete Endpoint Bypasses Delete Permission Check (critical 9.1) - [CVE-2023-39612](https://insights.sbomify.com/CVE-2023-39612/): Cross-site scripting in n/a (critical 9.0) - [CVE-2026-30934](https://insights.sbomify.com/CVE-2026-30934/): FileBrowser Quantum: Stored XSS in public share page via unsanitized share metadata (text/template misuse) (high 8.9) - [CVE-2021-46398](https://insights.sbomify.com/CVE-2021-46398/): Cross-Site Request Forgery in Filebrowser (high 8.8) - [CVE-2026-35604](https://insights.sbomify.com/CVE-2026-35604/): File Browser share links remain accessible after Share/Download permissions are revoked (high 8.2) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-32760 and fix it if it is affected. What it is: CVE-2026-32760 is a critical vulnerability in filebrowser, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32760 exists. Affected packages and fixed versions: - github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.62.0 - github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.62.0 - github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.62.0 - github.com/filebrowser/filebrowser (Go): affected all versions; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-32760/ (Markdown: https://insights.sbomify.com/CVE-2026-32760/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32760 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32760 - OSV: https://osv.dev/vulnerability/CVE-2026-32760 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-32760/ Summaries are generated and may contain mistakes; the official description above is the record.