No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 19 May 2026 13:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 18 May 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mlflow
Mlflow mlflow/mlflow |
|
| Vendors & Products |
Mlflow
Mlflow mlflow/mlflow |
Mon, 18 May 2026 20:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Incomplete Fix for CVE-2025-10279: Insecure Temporary Directory Permissions in mlflow/mlflow | |
| Weaknesses | CWE-378 | |
| References |
| |
| Metrics |
cvssV3_0
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: @huntr_ai
Published:
Updated: 2026-05-19T12:47:53.221Z
Reserved: 2026-03-13T15:15:45.839Z
Link: CVE-2026-4137
Updated: 2026-05-19T12:47:45.893Z
Status : Awaiting Analysis
Published: 2026-05-18T21:16:40.710
Modified: 2026-05-19T15:03:31.370
Link: CVE-2026-4137
No data.
OpenCVE Enrichment
Updated: 2026-05-18T22:00:12Z