# CVE-2026-28492: File Browser: Path Traversal in Public Share Links Exposes Files Outside Shared Directory

> Attackers with a public share link can browse and download files from sibling directories due to incorrect filesystem root calculation.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA: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:** 5 Mar 2026
- **Updated:** 6 Mar 2026
- **Also known as:** GHSA-mr74-928f-rw69, GO-2026-4585

## What is CVE-2026-28492?

CVE-2026-28492 is a high-severity path traversal vulnerability in filebrowser, published on 5 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, preview, rename and edit files. Prior to version 2.61.0, when a user creates a public share link for a directory, the withHashFile middleware in http/public.go uses filepath.Dir(link.Path) to compute the BasePathFs root. This sets the filesystem root to the parent directory instead of the shared directory itself, allowing anyone with the share link to browse and download files from all sibling directories. This issue has been patched in version 2.61.0.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

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.61.0 |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.61.0 |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.61.0 |
| `github.com/filebrowser/filebrowser` | Go | All versions | None |

Products: Filebrowser Filebrowser.

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

Upgrade github.com/filebrowser/filebrowser/v2 to 2.61.0 or later.

## Is CVE-2026-28492 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28492 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-28492 and fix it if it is affected.

What it is: CVE-2026-28492 is a high-severity path traversal vulnerability in filebrowser, published on 5 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-28492 exists.

Affected packages and fixed versions:
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.61.0
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.61.0
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.61.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-28492/ (Markdown: https://insights.sbomify.com/CVE-2026-28492/index.md)
```

## Sources

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

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