Skip to content
Heist/ feed
Medium

FileRise: Insecure default cryptographic key fallback in manual installs

Type: advisorySource: Official CVE List1 source record

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.

Announced Source revision 1
Original source ↗

CVE-2026-77427

Primary source · Revision 1

Imported from structured advisory data. Source references identify upstream records or fields; verify affected versions and your deployed configuration.

Security context

Source reference: cve:CVE-2026-77427

FileRise

Source reference: /containers/cna/affected/0/product

Affected versions
Not stated in this record
Fixed versions
Not stated in this record
Prerequisites
Not stated in this record

Structured affected-version data

Original package identities and version rules from this source.

[
  {
    "vendor": "error311",
    "product": "FileRise",
    "versions": [
      {
        "status": "affected",
        "version": ">= 3.9.0, < 3.22.0"
      }
    ]
  }
]
Related CVEs
CVE-2026-77427

Source reference: /cveMetadata/cveId

Publisher severity

medium

Source reference: /containers/cna/metrics

Event
#42092 · Revision 1
Added to Heist Feed
Publisher date
Read the original announcement