cve.bz

CVE-2026-54685 gtsteffaniak filebrowser: Observable Timing Discrepancy

5.3 mediumEPSS 0.3%Fix available

Medium (5.3) in gtsteffaniak filebrowser. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/gtsteffaniak/filebrowser/backend 0.0.0-20260317230626-af08800667b8.

On this page
FileBrowser Quantum is a free, self-hosted, web-based file manager. Prior to version 1.3.2-beta, the `/api/auth/login` authentication endpoint does not execute in constant time. When a non-existent username is supplied, the server returns a `401`/`403` response almost immediately. When a valid username is provided, the server performs a bcrypt password comparison, causing a measurable delay in the response time. Version 1.3.2-beta patches the issue.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 28th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-07-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-208 Observable Timing Discrepancy
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • github.com/gtsteffaniak/filebrowser/backend (Go): fixed in 0.0.0-20260317230626-af08800667b8

Ask an AI about this CVE

Show the promptExplain CVE-2026-54685 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-54685?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-54685?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-54685 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
gtsteffaniak filebrowser< 1.3.2-beta

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7789-65hx-f26wGogithub.com/gtsteffaniak/filebrowser/backend<0.0.0-20260317230626-af08800667b80.0.0-20260317230626-af08800667b8
GO-2026-4820Gogithub.com/gtsteffaniak/filebrowser/backend<0.0.0-20260317230626-af08800667b80.0.0-20260317230626-af08800667b8

Attack patterns (CAPEC)

  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-541 Application Fingerprinting Severity: Low
  • CAPEC-580 System Footprinting Likelihood: Low · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON