Secret disclosure via published fallback encryption key
Published Oct 14, 2026 · Updated Oct 14, 2026
Key fallback in FileRise 3.9.0 through 3.21.0 allows attackers to decrypt stored secrets using a published key on manual installs. The fr_resolve_persistent_tokens_key() resolver selects the legacy compatibility key when neither PERSISTENT_TOKENS_KEY nor metadata/persistent_tokens.key exists. Exploitation requires separately obtained account or configuration ciphertext; disclosure includes TOTP secrets and credentials, not demonstrated writes or service interruption.
Summary
What happened
Key fallback in FileRise 3.9.0 through 3.21.0 allows attackers to decrypt stored secrets using a published key on manual installs. The fr_resolve_persistent_tokens_key() resolver selects the legacy compatibility key when neither PERSISTENT_TOKENS_KEY nor metadata/persistent_tokens.key exists. Exploitation requires separately obtained account or configuration ciphertext; disclosure includes TOTP secrets and credentials, not demonstrated writes or service interruption.
The record
- CVE
- CVE-2026-77427
- Published
- Oct 14, 2026
- Updated
- Oct 14, 2026
- Vendor
- error311
- Product
- FileRise
- Classifications
- CWE-1188, CWE-798, T1552.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 14, 2026CVE publishedPublication date reported by the CVE source.
- Oct 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 3.9.0, < 3.22.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Isolated fallback-key decryption proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started