CVE-2026-77427
mediumFileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations.
FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. From 3.9.0 until 3.22.0, pristine manual FileRise installations without PERSISTENT_TOKENS_KEY or metadata/persistent_tokens.key can activate a published legacy compatibility key. If an attacker separately obtains ciphertext-bearing account or configuration files, the known fallback key can enable decryption of TOTP secrets or credentials. Docker installations already generated a unique persistent key, and existing installations are not automatically rotated because doing so could make encrypted state unreadable. This issue is fixed in version 3.22.0.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N Affected products
Not reported by the source (unknown — not "none").
Weakness classification (CWE)
Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://github.com/error311/FileRise/commit/b5213b66d4c668a45f1b7600aa62b79cb66ddbe6 security-advisories@github.com
- https://github.com/error311/FileRise/releases/tag/v3.22.0 security-advisories@github.com
- https://github.com/error311/FileRise/security/advisories/GHSA-g6p5-9cpq-mp5h security-advisories@github.com
- https://github.com/error311/FileRise/security/advisories/GHSA-g6p5-9cpq-mp5h 134c704f-9b21-4f2e-91b3-4a467353bcc0
