CVE-2026-69148: high-severity vulnerability in mlflow
MLflow: CreateModelVersion source validation does not check READ permission on referenced run_id
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.1epss 0.4%
MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. Prior to 3.15.0, CreateModelVersion accepts a run_id or model_id after _validate_source_run() or _validate_source_model() in mlflow/server/handlers.py verifies only path containment, allowing authenticated users to create a model version that references another user's artifact directory and read files through GET /model-versions/get-artifact without the required READ permission. This issue is fixed in version 3.15.0.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Affected products
mlflow · mlflowRelated CVEs — mlflow
In the same product, most dangerous first.
CVE-2026-64849CRITICALMLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebinding)EPSS 10.0%KEVCVE-2026-116690HIGHMLflow: Arbitrary file read on unauthenticated MLflow servers via prompt model version sourceEPSS 1.8%CVE-2026-116692CRITICALMLflow: Remote code execution on unauthenticated MLflow servers via third-party scorer deserialization importing caller-placed artifact modulesEPSS 0.7%CVE-2026-115886MEDIUMMLflow: SSRF on unauthenticated MLflow servers via third-party scorer kwargs in the scorer invoke, register, and GenAI evaluate endpointsEPSS 0.7%CVE-2026-53995HIGHMLflow 3.17.1 and prior Path Traversal via Trace ID APIEPSS 0.6%CVE-2026-79721HIGHCVE-2026-79721EPSS 0.5%