mlflow
Affected
- introduced
0, fixed3.11.0(ecosystem)
Fixed versions
3.11.0
Fix
- Fixed version
3.11.0pip install --upgrade mlflow==3.11.0
Advisory
Also known as: BIT-mlflow-2026-4137, CVE-2026-4137, GHSA-f2m9-wcf4-cwwx
MLFlow Creates a Temporary File With Insecure Permissions
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.
High Basis: CVSS v3 score 7, vector CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
0, fixed 3.11.0 (ecosystem)3.11.0
3.11.0pip install --upgrade mlflow==3.11.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: PyPA Advisory Database · CC BY 4.0