GHSA-R4V7-6WCG-GHJ5 is a medium-severity security vulnerability in github.com/gtsteffaniak/filebrowser (go), affecting versions < 0.0.0-20260522161427-fa5abc8c67f3a. It is fixed in 0.0.0-20260522161427-fa5abc8c67f3a.
Summary The /api/auth/login endpoint does not implement rate limiting, account lockout, or progressive backoff for repeated authentication failures. As a result, an attacker can perform unlimited login attempts against the endpoint. When combined with the username enumeration timing vulnerability, valid accounts can be identified and then brute-forced without restriction. The risk is further increased by a weak default password policy that only enforces a minimum length of five characters. Details The authentication endpoint /api/auth/login does not enforce any form of rate limiting, account lockout, or progressive backoff for repeated failed login attempts. Testing confirmed that the endpoint accepts an unlimited number of authentication attempts from the same client without delay or restriction. This allows attackers to repeatedly attempt password guesses against valid usernames. Secure authentication systems typically enforce request throttling, temporary account lockout, or progressive delays after repeated failed login attempts to mitigate brute-force attacks. Additional Context Password validation is implemented in backend/database/storage/bolt/user.go via checkPassword(), which only verifies that the supplied password length is greater than or equal to settings.Config.Auth.Methods.PasswordAuth.MinLength. In backend/common/settings/auth.go, the PasswordAuthConfig documents the default value of MinLength as 5. No additional complexity requirements, such as uppercase, lowercase, numeric, or special character checks, were identified in this code path. PoC The script below demonstrates the lack of rate limiting by performing a high volume automated authentication test. The script sends sequential login requests and monitors for HTTP 429 (Too Many Requests) status codes. Impact An attacker can perform unlimited authentication attempts against valid usernames. When combined with the username enumeration timing vulnerability, this enables targeted brute-force attacks against user accounts and increases the likelihood of credential compromise. Please let me know if you need any additional information or clarification. I'm happy to assist with testing or validating a fix.
GHSA-R4V7-6WCG-GHJ5 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (0.0.0-20260522161427-fa5abc8c67f3a). Upgrading removes the vulnerable code path.
go
github.com/gtsteffaniak/filebrowser (< 0.0.0-20260522161427-fa5abc8c67f3a)github.com/gtsteffaniak/filebrowser → 0.0.0-20260522161427-fa5abc8c67f3a (go)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether GHSA-R4V7-6WCG-GHJ5 is reachable in your applications. Explore open-source security for your team.
See if GHSA-R4V7-6WCG-GHJ5 is reachable in your applications. Get a demo
Already deployed Kodem? See GHSA-R4V7-6WCG-GHJ5 in your environment →Upgrade github.com/gtsteffaniak/filebrowser to 0.0.0-20260522161427-fa5abc8c67f3a or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
GHSA-R4V7-6WCG-GHJ5 is a medium-severity security vulnerability in github.com/gtsteffaniak/filebrowser (go), affecting versions < 0.0.0-20260522161427-fa5abc8c67f3a. It is fixed in 0.0.0-20260522161427-fa5abc8c67f3a.
GHSA-R4V7-6WCG-GHJ5 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
github.com/gtsteffaniak/filebrowser (go) versions < 0.0.0-20260522161427-fa5abc8c67f3a is affected.
Yes. GHSA-R4V7-6WCG-GHJ5 is fixed in 0.0.0-20260522161427-fa5abc8c67f3a. Upgrade to this version or later.
Whether GHSA-R4V7-6WCG-GHJ5 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade github.com/gtsteffaniak/filebrowser to 0.0.0-20260522161427-fa5abc8c67f3a or later.