High · CVSS 7.1CVE-2026-61844

FileRise: Folder Metadata Filename Collisions Bypass "read_own" IsolationCVE-2026-61844

Answer in brief

CVE-2026-61844 records a High severity (CVSS 7.1) vulnerability in FileRise: Folder Metadata Filename Collisions Bypass "read_own" Isolation. The current sources do not mark it as known exploited. The current feed maps error311/FileRise (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 14, 2026Updated Oct 14, 2026Source checked Oct 14, 2026First seen by HOL Oct 14, 2026Material review Oct 14, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.1
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps error311/FileRise (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
error311/FileRisegeneric	<3.18.0	3.18.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for error311/FileRise.
Review the reported fix. Update error311/FileRise to 3.18.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 14, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 14, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 14, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.