# CVE-2025-10279: Privilege Escalation in mlflow/mlflow

> An attacker with local write access to /tmp can exploit a race condition in MLflow's virtual environment creation to achieve arbitrary code execution.

- **Severity:** High 7.0 (`CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Feb 2026
- **Updated:** 2 Feb 2026
- **Also known as:** BIT-mlflow-2025-10279, GHSA-4x5p-f36r-mxxr, PYSEC-2026-1639

## What is CVE-2025-10279?

CVE-2025-10279 is a high-severity vulnerability in Lfprojects Mlflow, published on 2 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In mlflow version 2.20.3, the temporary directory used for creating Python virtual environments is assigned insecure world-writable permissions (0o777). This vulnerability allows an attacker with write access to the `/tmp` directory to exploit a race condition and overwrite `.py` files in the virtual environment, leading to arbitrary code execution. The issue is resolved in version 3.4.0.

Weakness: CWE-379 (Creation of Temporary File in Directory with Insecure Permissions)

## Which versions are affected by CVE-2025-10279?

4 open source packages ship an affected version, including mlflow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mlflow` | Bitnami | All versions | 3.4.0 |
| `mlflow` | PyPI | All versions | 3.4.0rc0 |
| `mlflow` | PyPI | All versions | 3.4.0rc0 |
| `mlflow` | PyPI | All versions | 3.4.0rc0 |

Products: Lfprojects Mlflow.

## How do I fix CVE-2025-10279?

Upgrade mlflow to a fixed version for your release line: 3.4.0 or 3.4.0rc0.

## Is CVE-2025-10279 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10279 exists.

## Other vulnerabilities in Lfprojects Mlflow

- [CVE-2026-64849](https://insights.sbomify.com/CVE-2026-64849/): MLflow Server-Side Request Forgery (critical 9.3, exploited in the wild)
- [CVE-2025-15379](https://insights.sbomify.com/CVE-2025-15379/): Command Injection in mlflow/mlflow (critical 10.0)
- [CVE-2024-0520](https://insights.sbomify.com/CVE-2024-0520/): Remote Code Execution due to Full Controlled File Write in mlflow/mlflow (critical 10.0)
- [CVE-2023-6977](https://insights.sbomify.com/CVE-2023-6977/): Path Traversal: '\..\filename' (critical 10.0)
- [CVE-2023-6709](https://insights.sbomify.com/CVE-2023-6709/): Improper Neutralization of Special Elements Used in a Template Engine in mlflow/mlflow (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-10279 and fix it if it is affected.

What it is: CVE-2025-10279 is a high-severity vulnerability in Lfprojects Mlflow, published on 2 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10279 exists.

Affected packages and fixed versions:
- mlflow (Bitnami): affected all versions; fixed in 3.4.0
- mlflow (PyPI): affected all versions; fixed in 3.4.0rc0
- mlflow (PyPI): affected all versions; fixed in 3.4.0rc0
- mlflow (PyPI): affected all versions; fixed in 3.4.0rc0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-10279/ (Markdown: https://insights.sbomify.com/CVE-2025-10279/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-10279
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-10279
- OSV: https://osv.dev/vulnerability/CVE-2025-10279

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-10279/
Summaries are generated and may contain mistakes; the official description above is the record.