# CVE-2026-32758: File Browser has an Access Rule Bypass via Path Traversal in Copy/Rename Destination Parameter > Authenticated users can bypass access rules to write or move files into restricted paths via path traversal in the rename destination parameter. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 Mar 2026 - **Updated:** 20 Mar 2026 - **Also known as:** GHSA-9f3r-2vgw-m8xp, GO-2026-4711 ## What is CVE-2026-32758? CVE-2026-32758 is a medium-severity path traversal vulnerability in filebrowser, published on 19 Mar 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. Versions 2.61.2 and below are vulnerable to Path Traversal through the resourcePatchHandler (http/resource.go). The destination path in resourcePatchHandler is validated against access rules before being cleaned/normalized, while the actual file operation calls path.Clean() afterward—resolving .. sequences into a different effective path. This allows an authenticated user with Create or Rename permissions to bypass administrator-configured deny rules (both prefix-based and regex-based) by injecting .. sequences in the destination parameter of a PATCH request. As a result, the user can write or move files into any deny-rule-protected path within their scope. However, this cannot be used to escape the user's BasePathFs scope or read from restricted paths. This issue has been fixed in version 2.62.0. Weakness: CWE-863 (Incorrect Authorization), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory) ## Which versions are affected by CVE-2026-32758? 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-32758? Upgrade github.com/filebrowser/filebrowser/v2 to 2.62.0 or later. ## Is CVE-2026-32758 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32758 exists. ## Other vulnerabilities in filebrowser - [CVE-2026-32760](https://insights.sbomify.com/CVE-2026-32760/): File Browser Self Registration Grants Any User Admin Access When Default Permissions Include Admin (critical 10.0) - [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) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-32758 and fix it if it is affected. What it is: CVE-2026-32758 is a medium-severity path traversal vulnerability in filebrowser, published on 19 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32758 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-32758/ (Markdown: https://insights.sbomify.com/CVE-2026-32758/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32758 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32758 - OSV: https://osv.dev/vulnerability/CVE-2026-32758 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-32758/ Summaries are generated and may contain mistakes; the official description above is the record.