# CVE-2024-6838: Uncontrolled Resource Consumption in mlflow/mlflow

> Attackers can cause MLflow UI unresponsiveness by creating experiments with excessively long names or artifact locations, leading to denial of service.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Mar 2025
- **Updated:** 20 Mar 2025
- **Also known as:** BIT-mlflow-2024-6838, GHSA-q3gw-8236-5jw4, PYSEC-2026-1658

## What is CVE-2024-6838?

CVE-2024-6838 is a medium-severity denial of service vulnerability in Lfprojects Mlflow, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In mlflow/mlflow version v2.13.2, a vulnerability exists that allows the creation or renaming of an experiment with a large number of integers in its name due to the lack of a limit on the experiment name. This can cause the MLflow UI panel to become unresponsive, leading to a potential denial of service. Additionally, there is no character limit in the `artifact_location` parameter while creating the experiment.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mlflow` | Bitnami | From 2.13.2 | 2.14.0 |
| `mlflow` | PyPI | All versions to 2.13.2 | None |
| `mlflow` | PyPI | All versions to 2.13.2 | None |
| `mlflow` | PyPI | All versions to 2.13.2 | None |

Products: Lfprojects Mlflow.

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

Upgrade mlflow to 2.14.0 or later.

## Is CVE-2024-6838 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6838 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-2024-6838 and fix it if it is affected.

What it is: CVE-2024-6838 is a medium-severity denial of service vulnerability in Lfprojects Mlflow, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6838 exists.

Affected packages and fixed versions:
- mlflow (Bitnami): affected from 2.13.2; fixed in 2.14.0
- mlflow (PyPI): affected all versions up to 2.13.2; no fix listed
- mlflow (PyPI): affected all versions up to 2.13.2; no fix listed
- mlflow (PyPI): affected all versions up to 2.13.2; no fix listed

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

## Sources

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

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