# File Browser has a DoS Vulnerability via Public Login API Advisory record · `GHSA-w5fm-68j4-fpc4` - **Identifiers:** `GHSA-w5fm-68j4-fpc4` · `CVE-2026-54092` · `GO-2026-5691` - **State:** Confirmed - **Severity:** CVSS 6.5 Medium - **Critical:** No - **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html) · [CWE-1284](https://cwe.mitre.org/data/definitions/1284.html) - **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md) · [CWE-1284](https://agentprime.io/advisories/tag/cwe-1284.md) - **Published:** 12 Jun 2026 - **Updated:** 21 Jul 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 12 Jun 2026, 21:51 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `github.com/filebrowser/filebrowser/v2` (Go): affected `<2.63.6`; fixed in `2.63.6` - `github.com/filebrowser/filebrowser` (Go): affected `<=1.11.0`; no fixed version yet ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Summary of the record's input: File Browser (github.com/filebrowser/filebrowser/v2) versions before 2.63.6 are affected, and the fix is in 2.63.6. The legacy module github.com/filebrowser/filebrowser at version 1.11.0 and earlier is also affected, with no fixed version listed. An attacker who can reach the login API can send a very large password, which drives CPU and memory use high enough to crash or stall the service. Upgrade github.com/filebrowser/filebrowser/v2 to 2.63.6 or later. No fix is listed for github.com/filebrowser/filebrowser, and the source gives few details on workarounds. Written 6 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0055, the 46th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 15:05 UTC: First seen by agentprime - 31 Oct 2026, 15:05 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-w5fm-68j4-fpc4) ## Sources - [GitHub Advisory Database: GHSA-w5fm-68j4-fpc4](https://github.com/advisories/GHSA-w5fm-68j4-fpc4) - [OSV: GHSA-w5fm-68j4-fpc4](https://osv.dev/vulnerability/GHSA-w5fm-68j4-fpc4) - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .