# CVE-2026-27611: FileBrowser Quantum: Password Protection Not Enforced on Shared File Links

> Attackers can bypass password protection on shared file links in FileBrowser Quantum to download files without authorization.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-8vrh-3pm2-v4v6, GO-2026-4546

## What is CVE-2026-27611?

CVE-2026-27611 is a high-severity authentication bypass vulnerability in gtsteffaniak filebrowser, published on 25 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

FileBrowser Quantum is a free, self-hosted, web-based file manager. Prior to versions 1.1.3-stable and 1.2.6-beta, when users share password-protected files, the recipient can completely bypass the password and still download the file. This happens because the API returns a direct download link in the details of the share, which is accessible to anyone with JUST THE SHARE LINK, even without the password. Versions 1.1.3-stable and 1.2.6-beta fix the issue.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel), CWE-287 (Improper Authentication), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-27611?

3 open source packages ship an affected version, including github.com/gtsteffaniak/filebrowser/backend. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/gtsteffaniak/filebrowser/backend` | Go | All versions | 0.0.0-20260221163904-dbcfba993b85 |
| `github.com/gtsteffaniak/filebrowser/backend` | Go | All versions | 0.0.0-20260221163904-dbcfba993b85 |
| `github.com/gtsteffaniak/filebrowser/backend` | Go | All versions | 0.0.0-20260221163904-dbcfba993b85 |

Products: Gtsteffaniak Filebrowser Quantum.

## How do I fix CVE-2026-27611?

Upgrade github.com/gtsteffaniak/filebrowser/backend to 0.0.0-20260221163904-dbcfba993b85 or later.

## Is CVE-2026-27611 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27611 exists.

## Other vulnerabilities in gtsteffaniak filebrowser

- [CVE-2026-44542](https://insights.sbomify.com/CVE-2026-44542/): FileBrowser Quantum: Unauthenticated Path Traversal in Public Share Delete Allows Arbitrary File Deletion (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-27611 and fix it if it is affected.

What it is: CVE-2026-27611 is a high-severity authentication bypass vulnerability in gtsteffaniak filebrowser, published on 25 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-27611 exists.

Affected packages and fixed versions:
- github.com/gtsteffaniak/filebrowser/backend (Go): affected all versions; fixed in 0.0.0-20260221163904-dbcfba993b85
- github.com/gtsteffaniak/filebrowser/backend (Go): affected all versions; fixed in 0.0.0-20260221163904-dbcfba993b85
- github.com/gtsteffaniak/filebrowser/backend (Go): affected all versions; fixed in 0.0.0-20260221163904-dbcfba993b85

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-27611/ (Markdown: https://insights.sbomify.com/CVE-2026-27611/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27611
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27611
- OSV: https://osv.dev/vulnerability/CVE-2026-27611

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-27611/
Summaries are generated and may contain mistakes; the official description above is the record.