Is CVE-2026-57489 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-57489 being exploited in the wild.

How severe is CVE-2026-57489?

High severity, with a CVSS score of 8.1, published 14 October 2026.

Which products and versions are affected?

Error311 FileRise before 3.16.0.

Am I affected by CVE-2026-57489?

Check whether you run Error311 FileRise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-57489: FileRise authentication bypass via proxy header spoofing

CVE-2026-57489 · Severity: high · CVSS 8.1 · Published 2026-10-14

FileRise is a self-hosted web-based file manager that allows users to upload, edit, and manage files. In deployments before version 3.16.0 with proxy-header authentication enabled, an attacker who can reach the backend application directly can forge identity headers to gain unauthorized access to any account, including administrator accounts, without entering a password or multi-factor authentication. This could allow an attacker to steal or modify files and take over the system.

Technologies: Error311 FileRise. Vendors: Error311.

Quick answers

Is CVE-2026-57489 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-57489 being exploited in the wild.
How severe is CVE-2026-57489?: High severity, with a CVSS score of 8.1, published 14 October 2026.
Which products and versions are affected?: Error311 FileRise before 3.16.0.
Is there a fix for CVE-2026-57489?: Yes: fixed in 3.16.0. Until then: Set the FR_TRUSTED_PROXIES environment variable to the IP address or CIDR range of your reverse proxy before upgrading to 3.16.0. Ensure the backend application port is not directly exposed to untrusted networks.</anigation> <parameter name="attack_vector">["network"] Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-57489 attacked?: It is in a web application.
Am I affected by CVE-2026-57489?: Check whether you run Error311 FileRise at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 3.16.0

Set the FR_TRUSTED_PROXIES environment variable to the IP address or CIDR range of your reverse proxy before upgrading to 3.16.0. Ensure the backend application port is not directly exposed to untrusted networks.</anigation> <parameter name="attack_vector">["network"]

Technical details

The vulnerability exists in proxy-header authentication: FileRise accepts the X-Remote-User header for authentication but fails to validate that the request originated from a trusted reverse proxy (FR_TRUSTED_PROXIES). An unauthenticated attacker with network access to the backend application port can inject a crafted X-Remote-User header to impersonate any user. The flaw is limited to deployments with AUTH_BYPASS enabled and proxy-header login configured, where the backend is directly reachable.

Affected products

error311 FileRise before 3.16.0

Timeline

2026-10-14: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.