Read the docs
TI-2026-74507 Aliases CVE-2026-77427

Hard-coded fallback encryption key in FileRise manual installs

Priority MEDIUM 60CWE-1188Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
Security bypass
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-798.

Summary

FileRise from 3.9.0 before 3.22.0 uses a published legacy compatibility key in pristine manual installations that lack PERSISTENT_TOKENS_KEY or metadata/persistent_tokens.key. An attacker who separately obtains ciphertext-bearing account or configuration files can use the known key to decrypt TOTP secrets or credentials. The flaw is a use of hard-coded credentials (CWE-798).

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Description from the CNA

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00349 28th percentileScored 2026-11-07
Fix Fixed FileRise (error311): 3.22.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
error311FileRise3.9.0 to before 3.22.03.22.0Patch availableCNA
  • FileRise Vendorerror311 Affected 3.9.0 to before 3.22.0 Fixed in 3.22.0 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:filerise:filerise:*:*:*:*:*:*:*:*——error311
  • cpe:2.3:a:filerise:filerise:*:*:*:*:*:*:*:* Versions — — ·error311

Remediation

Upgrade FileRise to version 3.22.0. Existing installations are not automatically rotated because doing so could make encrypted state unreadable.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

  • Fix · CNA FileRise (error311) Fixed in 3.22.0

Timeline

  1. 2026-10-15 Threatist record created from CVE-2026-77427
  2. 2026-10-16 Priority changed: MEDIUM → LOW
  3. 2026-10-20 CISA SSVC decision points changed
  4. 2026-10-20 Priority changed: LOW → MEDIUM

References

Other 3

  • TI-2026-74499 Unauthenticated file overwrite in FileRise via upload-enabled shares CVSS 3.1HIGH 8.2
  • TI-2026-25514 FileRise: Default Encryption Key Enables Token Forgery and Config Decryption CVSS 3.1HIGH 8.2
  • TI-2025-41705 FileRise vulnerable to Cross-Site Scripting (XSS) in SVG File Handling CVSS 3.1HIGH 8.9
  • TI-2026-25513 FileRise: WebDAV upload path bypasses filename validation enforced by regular uploads CVSS 3.1HIGH 8.8
  • TI-2026-74495 WebDAV authentication in FileRise skips TOTP two-factor check CVSS 3.1HIGH 8.1
  • TI-2026-74494 Authentication bypass in FileRise via spoofed reverse-proxy headers CVSS 3.1HIGH 8.1
See all 37 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences