# CVE-2026-54096: File Browser: Improper Access Control Occurs via Pre-Created Public Share for a Non-existent Path

> An attacker can create public shares for non-existent paths, which automatically expose files created later at those paths, leading to unauthorized data disclosure.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** GHSA-3q2p-72cj-682c, GO-2026-5096

## What is CVE-2026-54096?

CVE-2026-54096 is a high-severity missing authorization vulnerability in filebrowser, published on 25 Jun 2026. It can only be exploited from the same machine or local 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.7, `POST /api/share/<path>` accepts an authenticated request for an arbitrary path and stores a public share record without checking whether the target file currently exists. Later, when a file is created at that same path, the previously created public share immediately becomes valid and exposes the new file through `GET /api/public/dl/<hash>`. This vulnerability is fixed in 2.63.7.

Weakness: CWE-863 (Incorrect Authorization)

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

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

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

Upgrade to a fixed version.

## Is CVE-2026-54096 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54096 is a high-severity missing authorization vulnerability in filebrowser, published on 25 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54096 exists.

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.7
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.63.7
- github.com/filebrowser/filebrowser/v2 (Go): affected all versions; fixed in 2.63.7

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

## Sources

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

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