CVE-2026-61844FileRise: Folder Metadata Filename Collisions Bypass "read_own" Isolation
Updated under an hour ago ()
Does this affect you?
It affects error311 FileRise. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.25%, higher than 16% of scored CVEs.
Do this next
Free account, 1 product
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.
- CVSS
- 7.1 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L
- Weakness (CWE)
- CWE-706
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.25% (percentile 16)
- Assigned by
- GitHub_M
- NVD analysis
- Deferred
- Record last updated
- Oct 15, 2026
- First seen by InfoSec Signals
- Oct 14, 2026
Affected products
error311 FileRise error311:filerise (from the name) | before 3.18.0 | CNA record |
References
- https://github.com/error311/FileRise/security/advisories/GHSA-qpm8-pgmq-wxmhx-refsource-confirm
- https://github.com/error311/FileRise/commit/9ed1a38f00918849dbda30f54291d1451ed80d11x-refsource-misc
- https://github.com/error311/FileRise/releases/tag/v3.18.0x-refsource-misc
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.