# CVE-2026-55668: File Browser: ScopedFs follows a dangling symlink on write, letting a scoped user create files outside their scope

> An authenticated user can create files outside their assigned scope by exploiting dangling symlink validation in File Browser.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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:** 8 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** GHSA-8wc8-hf36-mjh9, GO-2026-6020

## What is CVE-2026-55668?

CVE-2026-55668 is a medium-severity path traversal vulnerability in filebrowser, published on 8 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

File Browser provides a web file managing interface. Prior to 2.63.16, ScopedFs validates the nearest existing ancestor of a dangling symlink as in scope and then follows the symlink during file creation, allowing an authenticated user with Create and Modify permissions to create attacker-controlled files outside the user's scope. This issue is fixed in version 2.63.16.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

4 open source packages ship an affected version, including github.com/filebrowser/filebrowser/v2 and github.com/filebrowser/filebrowser.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.63.16 |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.63.16 |
| `github.com/filebrowser/filebrowser/v2` | Go | All versions | 2.63.16 |
| `github.com/filebrowser/filebrowser` | Go | All versions | None |

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

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

## Is CVE-2026-55668 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55668 is a medium-severity path traversal vulnerability in filebrowser, published on 8 Jul 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-55668 exists.

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

## Sources

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

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