# CVE-2026-54097: File Browser: Cross-user unauthorized share-link deletion via unbounded prefix match in DeleteWithPathPrefix

> Low-privileged users can delete other users' share links by exploiting unbounded prefix matching in path deletion logic.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/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:** 25 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-5ww9-jg6q-38r7, GO-2026-5159

## What is CVE-2026-54097?

CVE-2026-54097 is a high-severity missing authorization vulnerability in filebrowser, published on 25 Jun 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. Prior to 2.63.6, a low-privileged authenticated user of filebrowser (with create + delete permissions in their own isolated scope) can silently destroy share-link records belonging to any other user — including the administrator — by performing a legitimate DELETE on a file in their own directory whose logical path happens to be a byte-prefix of another user's stored share.Link.Path. The file contents of the victim are not exposed, but the victim's share links are irrevocably wiped. This vulnerability is fixed in 2.63.6.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

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


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

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

Upgrade to a fixed version.

## Is CVE-2026-54097 being exploited?

There is no known exploitation of CVE-2026-54097 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54097 is a high-severity missing authorization vulnerability in filebrowser, published on 25 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54097 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/filebrowser/filebrowser (Go): affected all versions; no fix listed
- github.com/filebrowser/filebrowser (Go): affected all versions up to 1.11.0; no fix listed
- github.com/filebrowser/filebrowser (Go): affected all versions up to 1.11.0; no fix listed
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.63.6
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.63.6
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.63.6

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

## Sources

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

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