CVE-2026-72836
Case-insensitive filesystem flaw in FileBrowser allows cross-account file access.
Is CVE-2026-72836 being exploited?
Not confirmed. CVE-2026-72836 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.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-72836?
CVE-2026-72836 is rated Critical with a CVSS score of 9.2. 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-72836?
Yes. A fix has been recorded for CVE-2026-72836. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-72836 affect?
CVE-2026-72836 affects FileBrowser <2.63.19, Deployments with Signup + CreateUserDir enabled, Windows/NTFS and other case-insensitive filesystems. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-72836?
Upgrade to 2.63.19+ or disable Signup/CreateUserDir until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated attacker can self-register a colliding username and read, overwrite, or delete another user's files on case-insensitive filesystems.
Immediate action required
- affected< 2.63.19
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.