CVE-2026-61844 FileRise: Folder Metadata Filename Collisions Bypass "read_own" Isolation
A low-privileged user can bypass read_own isolation in FileRise by exploiting filename collisions to read and modify other users' files.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-61844?
CVE-2026-61844 is a high-severity vulnerability in error311 FileRise, published on 14 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.18.0, FileRise flattens logical folder paths into metadata filenames by replacing separators and spaces with hyphens, so distinct folders such as team/docs and team-docs can share one metadata file. Because uploader metadata is used to authorize read_own and ownership-restricted edits, a low-privileged user who controls one colliding folder, knows the target basename, and already has read_own access to the target folder can alter the metadata used by that folder, make the victim file appear attacker-owned, read it, and modify it when edit-own permission is also available. This issue is fixed in version 3.18.0.
Weakness: CWE-706
Which versions are affected by CVE-2026-61844?
How do I fix CVE-2026-61844?
No fix has been published for CVE-2026-61844 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-61844 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61844 exists.
Sources
Also known as GHSA-qpm8-pgmq-wxmh.