high CVSS 7.8

CVE-2026-4137·Python vulnerability

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
Software
Python
Fixed in
3.11.0
Published
2026-05-18

Affected versions

Until: 3.11.0

Fixed in: 3.11.0

How to fix this CVE

Upgrade MLflow to version 3.11.0 or later to remediate insecure temporary directory permissions that could allow local privilege escalation. The vulnerability affects MLflow's temporary directory creation functions which previously used overly permissive file modes, enabling unauthorized modification of model artifacts. Immediately patch all systems running MLflow, especially those with shared NFS mounts or multi-user environments.

sudo dnf update python3-mlflow || sudo pip3 install --upgrade mlflow>=3.11.0

Defensia detects this vulnerability

How to check if you are affected

  1. Check installed MLflow version: python3 -c "import mlflow; print(mlflow.__version__)"
  2. Verify vulnerable functions are in use: grep -r "get_or_create_nfs_tmp_dir\|_create_model_downloading_tmp_dir" /path/to/mlflow/installation/
  3. Check for world-writable or group-writable temp directories: find /tmp -type d -perm /077 -name "*mlflow*" -o -name "*model*" 2>/dev/null
  4. Confirm patch applied: python3 -c "import mlflow; assert mlflow.__version__ >= '3.11.0', 'MLflow not patched'" && echo 'Patched'

FAQ

What is CVE-2026-4137?

CVE-2026-4137 is a privilege escalation vulnerability in MLflow where temporary directories for model artifacts are created with overly permissive file permissions (world-writable or group-writable), allowing local attackers to inject malicious code into serialized Python objects that execute upon deserialization.

Is CVE-2026-4137 being actively exploited?

No, this vulnerability is not currently being actively exploited in the wild according to CISA records, and no public exploits are available at this time.

What versions of MLflow are affected by CVE-2026-4137?

All MLflow versions prior to 3.11.0 are affected by this vulnerability. MLflow 3.11.0 and later versions contain the necessary permission hardening fixes.

How do I check if my server is vulnerable to CVE-2026-4137?

Run `python3 -c "import mlflow; print(mlflow.__version__)"` and compare against 3.11.0. If your version is lower, you are vulnerable. Additionally, inspect temporary directory permissions with `find /tmp -type d -perm /077 -name "*mlflow*"` to identify world-writable directories.

Does Defensia detect CVE-2026-4137?

Yes — Defensia's CVE advisory scanner compares installed MLflow package versions against the NVD database. If MLflow is installed on a monitored server, CVE-2026-4137 will appear in your dashboard with remediation steps and severity assessment.

Related Python CVEs

CVE-2026-28505CVSS 10Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Prior to version 2.17.0, the str_eval() function in notification_handler.py implements a sandboxed eval() for notification text templates. The sandbox attempts to restrict callable names by inspecting code.co_names of the compiled code object. However, co_names only contains names from the outer code object. When a lambda expression is used, it creates a nested code object whose attribute accesses are stored in code.co_consts, NOT in code.co_names. The sandbox never inspects nested code objects. This issue has been patched in version 2.17.0.
CVE-2026-34938CVSS 10PraisonAI is a multi-agent teams system. Prior to version 1.5.90, execute_code() in praisonai-agents runs attacker-controlled Python inside a three-layer sandbox that can be fully bypassed by passing a str subclass with an overridden startswith() method to the _safe_getattr wrapper, achieving arbitrary OS command execution on the host. This issue has been patched in version 1.5.90.
CVE-2026-33054CVSS 10Mesop is a Python-based UI framework that allows users to build web applications. Versions 1.2.2 and below contain a Path Traversal vulnerability that allows any user supplying an untrusted state_token through the UI stream payload to arbitrarily target files on the disk under the standard file-based runtime backend. This can result in application denial of service (via crash loops when reading non-msgpack target files as configurations), or arbitrary file manipulation. This vulnerability heavily exposes systems hosted utilizing FileStateSessionBackend. Unauthorized malicious actors could interact with arbitrary payloads overwriting or explicitly removing underlying service resources natively outside the application bounds. This issue has been fixed in version 1.2.3.
CVE-2026-25632CVSS 10EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water distribution networks. Prior to 0.16.1, EPyT-Flow’s REST API parses attacker-controlled JSON request bodies using a custom deserializer (my_load_from_json) that supports a type field. When type is present, the deserializer dynamically imports an attacker-specified module/class and instantiates it with attacker-supplied arguments. This allows invoking dangerous classes such as subprocess.Popen, which can lead to OS command execution during JSON parsing. This also affects the loading of JSON files. This vulnerability is fixed in 0.16.1.
CVE-2026-9135CVSS 9.9IBM Langflow OSS 1.0.0 through 1.10.0 Langflow versions up to 1.9.2 (commit 94981c443d4918517b9e8163d70fc598dc33a32d) contain a code injection vulnerability in the Policies component's ToolGuard integration that bypasses the allow_custom_components=false security control. The vulnerability exists because the validation mechanism only checks the main component source code in node_template["code"]["value"] but fails to validate dynamic CodeInput fields that store generated ToolGuard Python files. Attackers can embed malicious Python code in these unvalidated dynamic fields, which are persisted in Flow.data and later executed server-side when a guarded tool is invoked through the ToolGuard runtime. This allows authenticated users with flow creation privileges to achieve arbitrary Python code execution on the backend despite custom component restrictions. The vulnerability can be escalated through cross-tenant flow manipulation via the agentic MCP update_flow_component_field tool, which accepts attacker-controlled user_id parameters, enabling attackers to inject malicious code into victim users' flows. When combined with publicly accessible flows and specific misconfigurations (AUTO_LOGIN=true, NEW_USER_IS_ACTIVE=true), the attack can be conducted with reduced authentication requirements.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-4137. Free for 1 server.

Get started free