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.
{
"cna_assigner": "GitHub_M",
"cwe_ids": [
"CWE-1188",
"CWE-798"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/77xxx/CVE-2026-77427.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "3.9.0"
},
{
"fixed": "3.22.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StringRangeExpression"
},
{
"range": [
{
"fixed": "b5213b66d4c668a45f1b7600aa62b79cb66ddbe6"
}
],
"source": "REFERENCES_COMMIT"
},
{
"original_tag": "v3.22.0",
"range": [
{
"fixed": "26ef2de90ceef4d1dae8853551d96a22be6d455c"
}
],
"source": "REFERENCES_TAG"
}
]
}