mlflow/mlflow: Creation of Temporary File in Directory with Insecure Permissions
CVE-2025-10279 is a high-severity creation of temporary file in directory with insecure permissions vulnerability in mlflow/mlflow from Mlflow, with a CVSS 3.0 base score of 7.0 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 3.4.0 as the first without the flaw, so updating mlflow/mlflow to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.24% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update mlflow/mlflow to 3.4.0 or a later version.
- Update Mlflow to 3.4.0 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Mlflow | mlflow/mlflow | before 3.4.0 | 3.4.0 |
| Lfprojects | Mlflow | before 3.4.0 | 3.4.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (huntr.dev).
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Creation of Temporary File in Directory with Insecure Permissions
The product creates a temporary file in a directory whose permissions allow unintended actors to determine the file's existence or otherwise access that file.
How developers prevent this class of flaw
- Many contemporary languages have functions which properly handle this condition. Older C temp file functions are especially susceptible.
- Try to store sensitive tempfiles in a directory which is not world readable -- i.e., per-user directories.
- Avoid using vulnerable temp file functions.
More Creation of Temporary File in Directory with Insecure Permissions vulnerabilities (CWE-379)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Technical write-ups (may include proof of concept)
- huntr.com/bounties/01d3b81e-13d1-43aa-b91a-443aec68bdc8Exploit, Third Party Advisory
Other vulnerabilities in mlflow/mlflow
- 8.1 High severity
- 7.7 High severity
- 9.0 Critical severity
- 9.6 Critical severity
- 7.8 High severity
- 8.6 High severity
Recent Creation of Temporary File in Directory with Insecure Permissions vulnerabilities
- 7.3 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.