Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Fri, 23 Oct 2026 00:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Error311
Error311 filerise |
|
| Vendors & Products |
Error311
Error311 filerise |
Tue, 20 Oct 2026 03:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 14 Oct 2026 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | FileRise: Insecure default cryptographic key fallback in manual installs | |
| Weaknesses | CWE-1188 CWE-798 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-20T02:09:06.968Z
Reserved: 2026-08-20T19:59:59.603Z
Link: CVE-2026-77427
Updated: 2026-10-20T02:09:01.456Z
Status : Deferred
Published: 2026-10-14T21:17:39.447
Modified: 2026-10-20T03:17:16.560
Link: CVE-2026-77427
No data.
OpenCVE Enrichment
Updated: 2026-10-22T22:45:13Z