Servers and applications
CVE-2026-4137
In mlflow/mlflow versions prior to 3.11.0, the `get_or_create_nfs_tmp_dir()` function in `mlflow/utils/file_utils.py` creates temporary directories with world-writable permissions (0o777), and the `_create_model_downloading_tmp_dir()` function in `mlflow/pyfunc/__init__.py` creates directories with group-writable permissions (0o770). These insecure permissions allow local attackers to tamper…
- Severity
- High 7.8
- Published
- 18 May 2026
- Last changed
- 24 Jul 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 3.11.0
- Exploit chance
- 0.2% in the next 30 daysHigher than 9% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- CWE-378
- Attack
- Needs local access · Needs a user account · No user action needed
- Attacker can
- Read data · Change data · Take it down
- CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H- Sources
- NVD
Description
In mlflow/mlflow versions prior to 3.11.0, the get_or_create_nfs_tmp_dir() function in mlflow/utils/file_utils.py creates temporary directories with world-writable permissions (0o777), and the _create_model_downloading_tmp_dir() function in mlflow/pyfunc/init.py creates directories with group-writable permissions (0o770). These insecure permissions allow local attackers to tamper with model artifacts, such as cloudpickle-serialized Python objects, and achieve arbitrary code execution when the tampered artifacts are deserialized via cloudpickle.load(). This vulnerability is particularly critical in environments with shared NFS mounts, such as Databricks, where NFS is enabled by default. The issue is a continuation of the vulnerability class addressed in CVE-2025-10279, which was only partially fixed.
Affected software
| Software | Affected versions |
|---|---|
MLflowServers and applications · cpe:a:lfprojects: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