What’s Vulnerable › Vulnerabilities
CVE-2026-77427: FileRise: Insecure default cryptographic key fallback in manual installs
- Severity: medium (CVSS 5.9 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.3% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-10-14 · updated 2026-10-20
- Weakness: CWE-798
Description
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.
Affected products
- error311 FileRise: from 3.9.0, < 3.22.0
References
- https://github.com/error311/FileRise/commit/b5213b66d4c668a45f1b7600aa62b79cb66ddbe6
- https://github.com/error311/FileRise/releases/tag/v3.22.0
- https://github.com/error311/FileRise/security/advisories/GHSA-g6p5-9cpq-mp5h
- https://github.com/error311/FileRise/security/advisories/GHSA-g6p5-9cpq-mp5h
Get alerted when CVE-2026-77427 or the next vulnerability affects your stack