{"vulnerability": "CVE-2026-61844", "sightings": [{"uuid": "44428441-ff83-466a-9408-8cb763f4acc5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-61844", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/117442131035228604", "content": "CVE-2026-61844 FileRise: Folder Metadata Filename Collisions Bypass \"read_own\" Isolation 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.\nhttps://www.cve.org/CVERecord?id=CVE-2026-61844https://github.com/error311/FileRise/security/advisories/GHSA-qpm8-pgmq-wxmhhttps://github.com/error311/FileRise/commit/9ed1a38f00918849dbda30f54291d1451ed80d11https://github.com/error311/FileRise/releases/tag/v3.18.0#error311 #FileRise#CVE_2026_61844#bot", "creation_timestamp": "2026-10-15T00:38:25.058075Z"}]}