{
 "version": "https://jsonfeed.org/version/1.1",
 "title": "mlflow: important CVE events",
 "home_page_url": "https://patchwire.jonathanross.dev/products/mlflow--mlflow/",
 "feed_url": "https://patchwire.jonathanross.dev/feeds/products/mlflow--mlflow/important.json",
 "authors": [
  {
   "name": "Patchwire"
  }
 ],
 "language": "en",
 "items": [
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-53995/disclosed",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-53995/",
   "title": "CVE-2026-53995 · mlflow · disclosed",
   "content_text": "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.",
   "date_published": "2026-10-19T21:05:16Z"
  },
  {
   "id": "tag:patchwire.jonathanross.dev,2026:CVE-2026-53995/fixed/pypi",
   "url": "https://patchwire.jonathanross.dev/cve/CVE-2026-53995/",
   "title": "CVE-2026-53995 · mlflow · fixed upstream (PyPI)",
   "content_text": "Fixed versions: mlflow 3.17.2.",
   "date_published": "2026-10-19T21:05:16Z"
  }
 ]
}