CuraSec

tag: Mlflow · 2 items

2026-08-20 · BleepingComputer · source ↗ #cisa-kev#mlflow#ai-ml-security
  • Engineer — Act: CISA’s active-exploitation warning effectively signals KEV listing; teams running MLflow in AI/ML pipelines should patch to the fixed version immediately and audit pipeline access logs for signs of prior compromise.
  • SOC/IR — Plan: The item confirms active exploitation but provides no IOCs or TTPs to hunt on; pull the full CISA advisory for indicators, then build detection rules targeting anomalous MLflow API or model-registry access patterns.
  • Leader — Plan: Confirm whether data science or engineering teams operate MLflow, then verify patching is tracked to completion — CISA exploitation warnings on AI/ML tooling are increasingly likely to surface in customer security questionnaires.
2026-08-19 · The Hacker News · source ↗ #mlflow#ssrf#cloud-credentials
  • Engineer — Act: MLflow is common in cloud-hosted ML pipelines and the SSRF flaw enables IMDS credential theft — active exploitation corroborated by two independent sources (watchTowr, VulnCheck). Patch MLflow to the fixed version immediately and audit IMDS endpoint access controls on any host running it.
  • SOC/IR — Act: Active exploitation of MLflow SSRF is confirmed by two independent sources, with cloud credential theft as the objective. Hunt for anomalous outbound requests to IMDS (169.254.169.254) originating from ML pipeline hosts, and check for SSRF-pattern HTTP requests against MLflow endpoints since early August.
  • Leader — Plan: If your org runs MLflow in cloud environments, active exploitation of this SSRF flaw creates cloud credential-theft risk for data science or AI teams. Confirm engineering has inventoried and patched MLflow deployments this sprint and review whether any cloud credentials may have been exposed.