Advisory record · GHSA-w5fm-68j4-fpc4

File Browser has a DoS Vulnerability via Public Login API

CVSS 6.5 MediumEPSS 0.0055 · 46th percentile

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.

PackageEcosystemAffectedFixed in
github.com/filebrowser/filebrowser/v2Go<2.63.62.63.6
github.com/filebrowser/filebrowserGo<=1.11.0No fixed version yet
Identifiers
GHSA-w5fm-68j4-fpc4 · CVE-2026-54092 · GO-2026-5691
Weakness (CWE)
CWE-400 · CWE-1284
Published
12 Jun 2026
Updated
21 Jul 2026

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

ScoreRatingCVSSVectorSource
6.5 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0055, the 46th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:05 UTC First seen by agentprime
  2. 31 Oct 2026, 15:05 UTC Confirmed by OSV

Sources

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.