# CVE-2024-27134: Excessive directory permissions in MLflow leads to local privilege escalation when using spark_udf

> Local attackers can escalate privileges via a race condition in MLflow's spark_udf API due to excessive directory permissions.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Nov 2024
- **Updated:** 25 Nov 2024
- **Also known as:** BIT-mlflow-2024-27134, GHSA-qpgc-w4mg-6v92, PYSEC-2024-224

## What is CVE-2024-27134?

CVE-2024-27134 is a high-severity vulnerability in Lfprojects Mlflow, published on 25 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Excessive directory permissions in MLflow leads to local privilege escalation when using spark_udf. This behavior can be exploited by a local attacker to gain elevated permissions by using a ToCToU attack. The issue is only relevant when the spark_udf() MLflow API is called.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition), CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2024-27134?

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


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

Products: Lfprojects Mlflow.

## How do I fix CVE-2024-27134?

Upgrade mlflow to 2.16.0 or later.

## Is CVE-2024-27134 being exploited?

There is no known exploitation of CVE-2024-27134 in the wild and no public exploit code.

## 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-2024-27134 and fix it if it is affected.

What it is: CVE-2024-27134 is a high-severity vulnerability in Lfprojects Mlflow, published on 25 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-27134 in the wild and no public exploit code.

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

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-2024-27134/ (Markdown: https://insights.sbomify.com/CVE-2024-27134/index.md)
```

## Sources

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

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