Servers and applications
CVE-2026-69148
CreateModelVersion source validation does not check READ permission on referenced run_id
- Severity
- Medium 6.5
- Published
- 4 Aug 2026
- Last changed
- 16 Sept 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 3.15.0
- Exploit chance
- 0.4% in the next 30 daysHigher than 31% of CVEs. EPSS by FIRST, 18 Nov 2026
- Weakness
- Missing authorization (CWE-862)
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N- Also known as
- GHSA-gqch-g4w5-7qcw
- Sources
- Project advisories (GitHub)
Description
The _validate_source_run and _validate_source_model functions in mlflow/server/handlers.py verify that a model version source path is within the artifact directory of a specified run or logged model, but do not check whether the caller has READ permission on that run or model. An authenticated MLflow user can therefore reference another user's run_id in CreateModelVersion, creating a model version whose artifact URI points at the victim's artifact directory. If the calling user has MANAGE permission on the registered model (which they do after creation), they can then read arbitrary files from the victim's artifact directory via GET /model-versions/get-artifact, bypassing the experiment-level READ permission gate on GET /get-artifact.
POST /api/2.0/mlflow/model-versions/create is protected: the caller must have UPDATE permission on the registered model. However, the source/run_id validation performed inside _validate_source_run only verifies path containment, not caller authorization:
Affected software
| Software | Affected versions |
|---|---|
MLflowServers and applications · github:mlflow/mlflow |
|
About MLflow
Python library
- Monthly downloads
- 30M+MLflow
- Weekly downloads (PyPI)
- 5,332,947PyPI Stats, 15 Nov 2026
- GitHub stars
- 28,816GitHub, 15 Nov 2026
- Forks
- 6,611GitHub, 15 Nov 2026
- Latest release
- v3.18.0GitHub, 15 Nov 2026
- Released
- 4 Nov 2026GitHub
- License
- Apache Software License 2.0Wikidata
- First published on GitHub
- 5 Jun 2018GitHub
Vulnerabilities in MLflow
- In our list
- 89
- Published in the last 12 months
- 37
- Critical, last 12 months
- 7
- High, last 12 months
- 15
- Known exploited
- 1
- CVE-2026-127202MLflow < 3.18.0 Path Traversal via model_id in log_outputs APIMedium 6.3 12 Nov 2026
- CVE-2026-118628Server-Side Request Forgery in the MLflow tracking server via client-supplied artifact locations and model version sourcesHigh 8.2 3 Nov 2026
- CVE-2026-118627MLflow SHAP load_explainer Deserialization of Untrusted Data Remote Code Execution VulnerabilityHigh 7.8 3 Nov 2026
- CVE-2026-118626MLflow Tracking Server Issues Missing Authorization Privilege Escalation VulnerabilityMedium 5.4 3 Nov 2026
- CVE-2026-118625MLflow Tracking Server Missing Authorization Privilege Escalation VulnerabilityMedium 6.3 3 Nov 2026
- CVE-2026-118624MLflow Tracking Server Jobs Missing Authorization Information Disclosure VulnerabilityMedium 5.4 3 Nov 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-69148
- GitHub Advisory Database https://github.com/advisories/GHSA-gqch-g4w5-7qcw
- github.com https://github.com/mlflow/mlflow/security/advisories/GHSA-gqch-g4w5-7qcw