CVE-2026-77427: CWE-798: Use of Hard-coded Credentials in error311 FileRise
Description
FileRise versions from 3.9.0 up to but not including 3.22.0 contain a vulnerability involving the use of a hard-coded legacy compatibility key. This key can be activated in pristine manual installations lacking a persistent tokens key, potentially allowing attackers who have obtained certain encrypted files to decrypt TOTP secrets or credentials. Docker installations are not affected due to unique persistent keys. The issue is fixed in version 3.22.0.
CVSS v3.1
Score 5.9medium
Affected software
error311
FileRise
pkg:github/error311/FileRiseRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
FileRise, a self-hosted web-based file manager, has a vulnerability (CVE-2026-77427) due to the use of a hard-coded legacy compatibility key in versions >=3.9.0 and <3.22.0. In manual installations without a persistent tokens key, this fallback key can be activated, enabling attackers who have obtained ciphertext-bearing account or configuration files to decrypt sensitive data such as TOTP secrets or credentials. Docker installations generate unique persistent keys and are not affected. The vulnerability is resolved in version 3.22.0.
Potential Impact
An attacker who obtains encrypted account or configuration files from vulnerable FileRise installations can use the known fallback key to decrypt TOTP secrets or credentials, potentially compromising account security. This vulnerability does not affect Docker installations due to unique persistent keys. There is no indication of active exploitation in the wild.
Mitigation Recommendations
Upgrade FileRise to version 3.22.0 or later, where the use of the hard-coded legacy compatibility key is fixed. Existing installations should rotate persistent tokens keys carefully to avoid making encrypted state unreadable. Docker installations are not affected and do not require action.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-08-20T19:59:59.603Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6acfeac92cdf04f656afb440
Added to database: 10/14/2026, 20:49:13 UTC
Last enriched: 10/14/2026, 21:04:08 UTC
Last updated: 10/14/2026, 21:28:12 UTC
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.