# CVE-2026-54092: File Browser: DoS Vulnerability on Public Login API

> An attacker can cause a denial of service by sending an arbitrarily large password to the login API, crashing the application and affecting the host system.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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-w5fm-68j4-fpc4, GO-2026-5691

## What is CVE-2026-54092?

CVE-2026-54092 is a medium-severity denial of service 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, unchecked passwords maximums allow for an arbitrarily large password to be passed into the login API. This spikes CPU and memory, and after testing, crashes, heavily lags any container created, and has even made my docker daemon start to send errors with status code 500 even after the container was destroyed. This vulnerability is fixed in 2.63.6.

Weakness: CWE-400 (Uncontrolled Resource Consumption), CWE-1284 (Improper Validation of Specified Quantity in Input)

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

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-54092?

Upgrade to a fixed version.

## Is CVE-2026-54092 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54092 is a medium-severity denial of service 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54092 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.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-54092/ (Markdown: https://insights.sbomify.com/CVE-2026-54092/index.md)
```

## Sources

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

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