CVE-2026-57489

Deferred Deferred - Pending Action

Authentication Bypass in FileRise via Proxy Headers

Publication date: 2026-10-14

Last updated on: 2026-10-14

Assigner: GitHub, Inc.

Description

FileRise is a self-hosted web-based file manager with multi-file upload, editing, and batch operations. Prior to 3.16.0, FileRise deployments with AUTH_BYPASS enabled trust the configured reverse-proxy identity header without verifying that the request originated from FR_TRUSTED_PROXIES. When the backend application port is reachable directly, an unauthenticated attacker can supply X-Remote-User and obtain a session for the asserted account, including an administrator account, without a password or MFA. The flaw is limited to deployments that enable proxy-header authentication and expose an untrusted path to the backend. This issue is fixed in version 3.16.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-10-14

Last Modified

2026-10-14

Generated

2026-10-19

AI Q&A

2026-10-15

EPSS Evaluated

2026-10-18

NVD

CVE-2026-57489

EUVD

EUVD-2026-101634

Affected Vendors & Products

Vendor	Product	Version / Range
error311	FileRise	< 3.16.0

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-290	This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.

Attack-Flow Graph

Executive Summary

FileRise before 3.16.0 has an authentication bypass when AUTH_BYPASS is enabled. It trusts reverse-proxy identity headers without verifying the request came from trusted proxies. If the backend port is exposed directly, attackers can set X-Remote-User to impersonate any user, including administrators, without credentials or MFA.

Detection Guidance

Check if FileRise is running a version prior to 3.16.0 by inspecting the version file or running commands like 'curl -s http://<target>/version' or checking the package manager for installed versions. Verify if AUTH_BYPASS is enabled in the configuration and if the backend port is exposed to untrusted networks.

Impact Analysis

An attacker could gain full access to your FileRise instance, steal sensitive files, modify or delete data, or escalate privileges to take over the entire system. This includes accessing administrator accounts and all managed files.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating GDPR's data protection requirements and HIPAA's security rules for protected health information. Organizations may face compliance violations, fines, or legal consequences due to data breaches.

Mitigation Strategies

Upgrade FileRise to version 3.16.0 or later immediately. Disable AUTH_BYPASS if not required. Ensure the backend application port is not exposed to untrusted networks by configuring firewalls or reverse proxy settings to restrict access.

Hi! I’m here to help you understand CVE-2026-57489. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70