← back to feed
CVE-2026-57492

CVE-2026-57492

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

GHSA-g555-3rg9-wrq8 ↗EUVD-2026-101664 ↗

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 3.16.0
CWE-306 Missing Authentication for Critical Function
ETK-2026-1842Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss7.4cna vendorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
4d 10h 45msince last run
8mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+55h31m
0
+2h
+4h
+6h
+8h
+10h

description

FileRise versions before 3.16.0 can reopen setup mode when the user-store file is empty or missing. An unauthenticated remote attacker could then create an administrator account if storage loss, truncation, or another failure has emptied that file.

mitigation

Upgrade FileRise to version 3.16.0 or later. Protect and monitor the user-store file to reduce the chance that it is deleted or truncated before upgrading.

fixed in 3.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.27%18th percentile
agent run time
8m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-14 20:21Z
Δ 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:21Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-57492

this entry in the feed

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

{
  "etk_id": "ETK-2026-1842",
  "cve_id": "CVE-2026-57492",
  "display_id": "CVE-2026-57492",
  "ghsa_id": "GHSA-g555-3rg9-wrq8",
  "euvd_id": "EUVD-2026-101664",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated administrator creation in FileRise setup mode",
  "summary": "FileRise versions before 3.16.0 can reopen setup mode when the user-store file is empty or missing. An unauthenticated remote attacker could then create an administrator account if storage loss, truncation, or another failure has emptied that file.",
  "mitigation": "Upgrade FileRise to version 3.16.0 or later. Protect and monitor the user-store file to reduce the chance that it is deleted or truncated before upgrading.",
  "vendor": "error311",
  "product": "FileRise",
  "affected": [
    {
      "affected_notes": [
        "≤ 3.15.0"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [
        "3.16.0"
      ],
      "package_name": "error311/FileRise",
      "purl": null
    }
  ],
  "cwes": [
    306
  ],
  "cvss_score": 7.4,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": 0.0027,
  "epss_percentile": 0.1867,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 7.7493489,
  "t0_at": "2026-10-14T20:21:15.070000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-14T20:21:15.070000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T20:21:15.070000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-57492"
    }
  }
}

published 2026-10-17 03:44Z
last change 2026-10-21 04:45Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.