CVE-2026-57489

waiting for further signalsZero needs more public information before it can validate it.

GHSA-98pg-w3jp-r8fv ↗EUVD-2026-101634 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
error311 FileRise ≤ 3.15.0
fixed in v3.16.0
CWE-290 Authentication Bypass by Spoofing
ETK-2026-1642Zero's internal tracking ID, independent of the CVE number., permanent identifier
6d 15h 26msince last run
24mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+9h04m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

FileRise versions before 3.16.0 can accept an unverified reverse-proxy identity header when proxy-header authentication is enabled. An unauthenticated attacker may obtain a session as an asserted user, including an administrator, if they can directly reach the backend application port.

mitigation

Upgrade FileRise to version 3.16.0 or later. Until upgraded, disable proxy-header authentication or prevent untrusted networks from reaching the backend application port.

fixed in v3.16.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.50%41st percentile
agent run time
24m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-14 20:16Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-14 20:16Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-57489

{
  "etk_id": "ETK-2026-1642",
  "cve_id": "CVE-2026-57489",
  "display_id": "CVE-2026-57489",
  "ghsa_id": "GHSA-98pg-w3jp-r8fv",
  "euvd_id": "EUVD-2026-101634",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass through proxy headers in FileRise",
  "summary": "FileRise versions before 3.16.0 can accept an unverified reverse-proxy identity header when proxy-header authentication is enabled. An unauthenticated attacker may obtain a session as an asserted user, including an administrator, if they can directly reach the backend application port.",
  "mitigation": "Upgrade FileRise to version 3.16.0 or later. Until upgraded, disable proxy-header authentication or prevent untrusted networks from reaching the backend application port.",
  "vendor": "error311",
  "product": "FileRise",
  "affected": [
    {
      "affected_notes": [
        "≤ 3.15.0"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "v3.16.0"
      ],
      "package_name": "error311/FileRise",
      "purl": null
    }
  ],
  "cwes": [
    290
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.005,
  "epss_percentile": 0.4165,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 24.24408675,
  "t0_at": "2026-10-14T20:16:00.021000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-14T20:16:00.021000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T20:16:00.021000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-57489"
    }
  }
}

published 2026-10-15 04:56Z
last change 2026-10-21 20:26Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.