High

MLflow 3.17.1 and prior Path Traversal via Trace ID API

Type: advisorySources: OSV

MLflow 3.17.1 and earlier contains a path traversal vulnerability in the FileStore tracking backend that allows unauthenticated attackers to control filesystem paths by submitting a crafted trace ID containing traversal sequences to the POST /api/3.0/mlflow/traces endpoint. Attackers can exploit FileStore.start_trace() to write trace_info.yaml, request_metadata, and tag files with attacker-controlled metadata outside the intended experiment trace directory, subject to the server process's filesystem permissions. FileStore is the default tracking backend before MLflow 3.7.0 and opt-in thereafter (the default changed to a SQLite database), so deployments in the earlier part of the affected range are vulnerable without special configuration while later ones are affected only when FileStore is explicitly selected.

Products: Not specified
Affected versions: Not specified
Fixed versions: Not specified
CVEs: CVE-2026-53995
Confirmed fixed CVEs: Not specified
Updated in this feed: 4 Nov 2026, 08:35 UTC · Revision 1

Source evidence

MLflow 3.17.1 and prior Path Traversal via Trace ID API

core-osv · Original source

Published 19 Oct 2026, 21:05 UTC

osv:CVE-2026-53995

Complete source record

{
  "id": "93cb58d37d6f741511134f37db226798a1fce629058e1021686478a882ffb1bb",
  "url": "https://osv.dev/vulnerability/CVE-2026-53995",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "MLflow 3.17.1 and prior Path Traversal via Trace ID API",
    "summary": "MLflow 3.17.1 and earlier contains a path traversal vulnerability in the FileStore tracking backend that allows unauthenticated attackers to control filesystem paths by submitting a crafted trace ID containing traversal sequences to the POST /api/3.0/mlflow/traces endpoint. Attackers can exploit FileStore.start_trace() to write trace_info.yaml, request_metadata, and tag files with attacker-controlled metadata outside the intended experiment trace directory, subject to the server process's filesystem permissions. FileStore is the default tracking backend before MLflow 3.7.0 and opt-in thereafter (the default changed to a SQLite database), so deployments in the earlier part of the affected range are vulnerable without special configuration while later ones are affected only when FileStore is explicitly selected.",
    "evidence": "osv:CVE-2026-53995",
    "products": [],
    "severity": "high",
    "structured": {
      "id": "CVE-2026-53995",
      "aliases": [
        "BIT-mlflow-2026-53995",
        "CVE-2026-53995",
        "GHSA-wqmh-qccw-pqwf"
      ],
      "metrics": [
        {
          "type": "CVSS_V4",
          "score": "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"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/mlflow/mlflow",
              "type": "GIT",
              "events": [
                {
                  "introduced": "0"
                },
                {
                  "last_affected": "7fc49ae9fcd65ed125e46cf68b976060e5a38c77"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "range": [
                      {
                        "introduced": "0"
                      },
                      {
                        "last_affected": "3.17.1"
                      }
                    ],
                    "source": "AFFECTED_FIELD",
                    "strategy": "StandardRange"
                  },
                  {
                    "range": [
                      {
                        "introduced": "0"
                      },
                      {
                        "last_affected": "3.17.1"
                      }
                    ],
                    "source": "DESCRIPTION"
                  }
                ]
              }
            }
          ],
          "versions": [
            "v3.17.1",
            "v3.17.0",
            "ts/typesafe/v0.4.0",
            "ts/v0.4.0",
            "ts/v0.3.1",
            "ts/v0.3.0",
            "ts/v0.3.0-rc.0",
            "ts/v0.2.0",
            "ts/v0.2.0-rc.2",
            "ts/v0.2.0-rc.1",
            "model-catalog/latest",
            "nightly",
            "v3.0.0",
            "v2.2.0",
            "v1.7.0",
            "1.0.0",
            "v0.8.1",
            "v0.8.0",
            "v0.7",
            "v0.6.0",
            "v0.5.0",
            "v0.4.2",
            "v0.4.1",
            "v0.4.0",
            "v0.3.0",
            "v0.2.1",
            "v0.2.0"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53995.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:33.852534607Z",
      "provider": "osv",
      "references": [
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53995.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-53995",
        "https://www.vulncheck.com/advisories/mlflow-path-traversal-via-trace-id-api",
        "https://github.com/mlflow/mlflow/pull/26842",
        "https://github.com/mlflow/mlflow",
        "https://github.com/SaiTeja-Erukude/CVE-2026-53995-mlflow-path-traversal"
      ],
      "provider_metadata": {
        "cwe_ids": [
          "CWE-22"
        ],
        "cna_assigner": "VulnCheck",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53995.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-53995",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 501151,
  "published_at": "2026-10-19T21:05:16.53+00:00"
}