# CVE-2026-32761: File Browser has an Authorization Policy Bypass in its Public Share Download Flow > Authenticated users with share privileges can bypass download restrictions to exfiltrate files via public share links in File Browser. - **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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:** 21 Mar 2026 - **Also known as:** GHSA-68j5-4m99-w9w9, GO-2026-4738 ## What is CVE-2026-32761? CVE-2026-32761 is a medium-severity missing authorization 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.0 and below contain a permission enforcement bypass which allows users who are denied download privileges (perm.download = false) but granted share privileges (perm.share = true) to exfiltrate file content by creating public share links. While the direct raw download endpoint (/api/raw/) correctly enforces the download permission, the share creation endpoint only checks Perm.Share, and the public download handler (/api/public/dl/) serves file content without verifying that the original file owner has download permission. This means any authenticated user with share access can circumvent download restrictions by sharing a file and then retrieving it via the unauthenticated public download URL. The vulnerability undermines data-loss prevention and role-separation policies, as restricted users can publicly distribute files they are explicitly blocked from downloading directly. This issue has been fixed in version 2.62.0. Weakness: CWE-863 (Incorrect Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-284 (Improper Access Control) ## Which versions are affected by CVE-2026-32761? 4 open source packages ship an affected version, including https://github.com/filebrowser/filebrowser, github.com/filebrowser/filebrowser and github.com/filebrowser/filebrowser/v2. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `https://github.com/filebrowser/filebrowser` | Go | All versions to 2.61.0 | None | | `https://github.com/filebrowser/filebrowser` | Go | All versions to 2.61.0 | None | | `github.com/filebrowser/filebrowser` | Go | All versions | None | | `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.62.0 | Products: Filebrowser Filebrowser. ## How do I fix CVE-2026-32761? Upgrade to a fixed version. ## Is CVE-2026-32761 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32761 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-32761 and fix it if it is affected. What it is: CVE-2026-32761 is a medium-severity missing authorization 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-32761 exists. Affected packages and fixed versions: - https://github.com/filebrowser/filebrowser (Go): affected all versions up to 2.61.0; no fix listed - https://github.com/filebrowser/filebrowser (Go): affected all versions up to 2.61.0; no fix listed - github.com/filebrowser/filebrowser (Go): affected all versions; no fix listed - github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.62.0 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-32761/ (Markdown: https://insights.sbomify.com/CVE-2026-32761/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32761 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32761 - OSV: https://osv.dev/vulnerability/CVE-2026-32761 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-32761/ Summaries are generated and may contain mistakes; the official description above is the record.