← back to feed
CVE-2026-53995

CVE-2026-53995

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

GHSA-wqmh-qccw-pqwf ↗EUVD-2026-104633 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−1.9dkevAttacks confirmed in the real world.
mlflow <= 3.17.1
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
ETK-2026-2089Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss8.8cna vendorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N
1d 17h 41msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
public poc−1.9dtrigger signal (cve.org) +0dwaiting for further signals+0.1d
−1d
0

description

MLflow FileStore tracking backends through version 3.17.1 are affected by a path traversal vulnerability. An unauthenticated remote attacker may cause files containing attacker-controlled metadata to be written outside the intended trace directory with the MLflow server process's permissions. Deployments before 3.7.0 commonly use FileStore by default; later deployments are affected only when FileStore is explicitly configured.

mitigation

Stop using the FileStore tracking backend and use a database-backed tracking store such as SQLite instead. Restrict unauthenticated access to the MLflow tracking API and limit the server process's filesystem permissions.

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.
–
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.56%45th percentile
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 21:05Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
−1.9d
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-19 21:05Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-53995
  2. 2026-10-19 21:50Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2089",
  "cve_id": "CVE-2026-53995",
  "display_id": "CVE-2026-53995",
  "ghsa_id": "GHSA-wqmh-qccw-pqwf",
  "euvd_id": "EUVD-2026-104633",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Path traversal in MLflow FileStore tracking backend",
  "summary": "MLflow FileStore tracking backends through version 3.17.1 are affected by a path traversal vulnerability. An unauthenticated remote attacker may cause files containing attacker-controlled metadata to be written outside the intended trace directory with the MLflow server process's permissions. Deployments before 3.7.0 commonly use FileStore by default; later deployments are affected only when FileStore is explicitly configured.",
  "mitigation": "Stop using the FileStore tracking backend and use a database-backed tracking store such as SQLite instead. Restrict unauthenticated access to the MLflow tracking API and limit the server process's filesystem permissions.",
  "vendor": "mlflow",
  "product": "mlflow",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 3.17.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "mlflow",
      "purl": null
    }
  ],
  "cwes": [
    22
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N",
  "epss_score": 0.0056,
  "epss_percentile": 0.4559,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.3183764,
  "t0_at": "2026-10-19T21:05:16.530000+00:00",
  "signals": {
    "public_poc": {
      "at": "2026-10-17T22:20:51+00:00",
      "days": -1.9475177083333333,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T21:05:16.530000+00:00",
      "url": "https://github.com/SaiTeja-Erukude/CVE-2026-53995-mlflow-path-traversal"
    },
    "trigger_signal": {
      "at": "2026-10-19T21:05:16.530000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T21:05:16.530000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-53995"
    }
  }
}

published 2026-10-19 21:41Z
last change 2026-10-21 13:29Z

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.