CVE-2026-77427 FileRise: Insecure default cryptographic key fallback in manual installs
Attackers with access to ciphertext files can decrypt TOTP secrets or credentials using a known fallback key in manual FileRise installations.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-77427?
CVE-2026-77427 is a medium-severity vulnerability in error311 FileRise, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Which versions are affected by CVE-2026-77427?
How do I fix CVE-2026-77427?
No fix has been published for CVE-2026-77427 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-77427 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77427 exists.
Sources
Also known as GHSA-g6p5-9cpq-mp5h.