CVE-2026-62685
File Browser signup normalization allows account collision and cross-account file access.
Is CVE-2026-62685 being exploited?
Not confirmed. CVE-2026-62685 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.55% probability of exploitation in the next 30 days.
How severe is CVE-2026-62685?
CVE-2026-62685 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-62685?
Yes. A fix has been recorded for CVE-2026-62685. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-62685 affect?
CVE-2026-62685 affects File Browser < 2.63.17, Self-hosted instances with Signup=true and CreateUserDir=true. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-62685?
Upgrade to File Browser 2.63.17 or disable Signup/CreateUserDir until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Username normalization collisions during signup allow a second registrant to gain full read/write access to another user's files.
Immediate action required
- affected< 2.63.17
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.