Skip to content

GHSA-f2m9-wcf4-cwwx BIT-mlflow-2026-4137 CVE-2026-4137 PYSEC-2026-2655

MLFlow Creates a Temporary File With Insecure Permissions

High PyPI
Severity
7.0 / 10
High · CVSS 3.0
Exploit chance (EPSS)
0.19%
Chance of exploitation in the next 30 days. Higher than 9.05% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-378 Creation of Temporary File With Insecure Permissions
Fix
3.11.0
Upgrade mlflow to this version or later

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 versions

PyPI

PackageVulnerableFixed in
mlflow
>= 1.26.0, < 3.11.0
3.11.0
mlflow
< 3.11.0
3.11.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

mlflow PyPI → 3.11.0

pip
pip install --upgrade "mlflow>=3.11.0"
poetry
poetry add "mlflow>=3.11.0"
uv
uv add "mlflow>=3.11.0"

Severity breakdown

CVSS 3.0 7.0

CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-378: Creation of Temporary File With Insecure Permissions

Opening temporary files without appropriate measures or controls can leave the file, its contents and any function that it impacts vulnerable to attack.

How to prevent it
  • Requirements: Many contemporary languages have functions which properly handle this condition. Older C temp file functions are especially susceptible.
  • Implementation: Ensure that you use proper file permissions. This can be achieved by using a safe temp file function. Temporary files should be writable and readable only by the process that owns the file.
  • Implementation: Randomize temporary file names. This can also be achieved by using a safe temp-file function. This will ensure that temporary files will not be created in predictable places.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-7gwp-5pfp-969j
MLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebinding)
Critical Known exploited Also affects mlflow
GHSA-26p8-2jq9-3vq9
MLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifact modules
Critical Also affects mlflow
GHSA-j7qq-vr8c-xvw3
MLflow CrewAI autologging records LLM provider API keys in logged trace spans
Medium Also affects mlflow
GHSA-m65p-9j7q-6w33
MLflow vulnerable to arbitrary file read on unauthenticated servers via prompt model version source
High Also affects mlflow
GHSA-2wqp-q3c6-ccj5
MLflow: SSRF on unauthenticated MLflow servers via third-party scorer kwargs in the scorer invoke, register, and GenAI evaluate endpoints
Medium Also affects mlflow
GHSA-wqmh-qccw-pqwf
MLflow FileStore trace IDs allow path traversal and arbitrary file writes
High Also affects mlflow
GHSA-gqvg-gmmx-x4hm
MLFLOW_ALLOW_PICKLE_DESERIALIZATION=False safety control bypassed by mlflow.statsmodels flavor — RCE via crafted model artifact
High Also affects mlflow
GHSA-h7x2-h6g9-p789
MLflow AI Gateway permits SSRF through an unvalidated api_base
High Also affects mlflow
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor