Read the docs
TI-2026-74464 Aliases CVE-2026-55498

Symlink following in FileRise exposes files outside shared folders

Priority MEDIUM 55CWE-59Published · Updated

Key facts

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

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

FileRise before 3.15.0 has a flaw in public shared-folder links with subfolder browsing enabled. Such links follow symbolic links inside the shared folder to sibling directories under the upload root, because symlinks are resolved without the original shared folder as the real path boundary (CWE-59). An unauthenticated attacker with a valid share token can list, download, or zip files outside the folder that was shared.

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. Prior to 3.15.0, FileRise public shared-folder links with subfolder browsing enabled can follow a symbolic link inside the shared folder to a sibling directory under the upload root. An unauthenticated holder of a valid share token can use shared-folder listing, direct download, or ZIP creation to access files outside the folder that was actually shared. The flaw occurs because the affected shared-folder paths resolve symlinks without enforcing the original shared folder as the real-path boundary. This issue is fixed in version 3.15.0.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00331 26th percentileScored 2026-11-07
Fix Fixed FileRise (error311): 3.15.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
error311FileRisebefore 3.15.03.15.0Patch availableCNA
  • FileRise Vendorerror311 Affected before 3.15.0 Fixed in 3.15.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

Update FileRise to version 3.15.0, which fixes this issue.

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

  • Fix · CNA FileRise (error311) Fixed in 3.15.0

Timeline

  1. 2026-10-15 Threatist record created from CVE-2026-55498
  2. 2026-10-16 CISA SSVC decision points changed
  3. 2026-10-16 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