Advisory

PYSEC-2026-2655

Also known as: BIT-mlflow-2026-4137, CVE-2026-4137, GHSA-f2m9-wcf4-cwwx

Summary

MLFlow Creates a Temporary File With Insecure Permissions

Details

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.

Severity

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

Dates

Published
2026-07-13 15:19 UTC
Modified
2026-07-13 16:43 UTC

Affected packages and fixes

mlflow

PyPI · All systems

Affected

  • introduced 0, fixed 3.11.0 (ecosystem)

Fixed versions

3.11.0

Fix

  • Fixed version 3.11.0
    pip install --upgrade mlflow==3.11.0

Fix 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

View this record on OSV.dev

Source

Source: PyPA Advisory Database · CC BY 4.0

Sources & licences