CVE-2025-10279: mlflow Insecure Temporary File Permissions Leading to Code Execution
Summary
CVE-2025-10279: mlflow Creates of Temporary File in Directory with Insecure Permissions. Affects mlflow versions < 3.4.0rc0. Fixed in 3.4.0rc0. How to fix ↓
Also tracked for
- mlflow · Bitnami
The same CVE-2025-10279 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
mlflow is an open-source platform designed for managing the machine learning lifecycle, including experimentation, reproducibility, and deployment. It provides tools for tracking experiments, packaging code into reproducible runs, and sharing and deploying models. However, in version 2.20.3, mlflow has a vulnerability related to the creation of temporary files in a directory with insecure permissions, which can expose users to significant security risks.
Vulnerability Detail
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 arises from the improper handling of file permissions, making it possible for malicious actors to manipulate the environment and execute unauthorized code.
How To Fix
Latest published version: 3.17.2 as of 23 Oct 2026
pip install --upgrade "mlflow==3.17.2"Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
3.4.0rc0
This is the first release that contains the fix.
pip install --upgrade "mlflow==3.4.0rc0"Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, you can change the permissions of the /tmp directory to restrict write access for unauthorized users. This can be done using the following command: chmod 1777 /tmp. However, this is not a permanent solution and updating mlflow is strongly recommended.
Conclusion
The vulnerability identified as CVE-2025-10279 in mlflow poses a significant risk due to insecure temporary file permissions that could lead to arbitrary code execution. Users are strongly encouraged to update to the latest version to mitigate this risk. For those unable to update immediately, a temporary workaround is available, but it is not a substitute for a proper fix.
See every vulnerability recorded for mlflow →
FAQ
The CVSS score of this vulnerability is 7.0, indicating a high severity level.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
If exploited, this vulnerability could allow an attacker to execute arbitrary code within the context of the affected Python virtual environment, potentially compromising the entire application.
Yes, mlflow version 3.4.0rc0 and later versions have resolved this vulnerability and are safe to use.
If an immediate update is not possible, consider implementing the workaround by adjusting the permissions of the /tmp directory to limit write access.
Related vulnerabilities
Recent vulnerabilities recorded for mlflow.
