What is the CVSS score of CVE-2024-6838?

CVE-2024-6838 has a CVSS 3.1 base score of 5.3 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L. EPSS exploitation probability: 0.1%.

Which versions of Mlflow are affected by CVE-2024-6838?

Organizations using mlflow/mlflow should be aware of moderate risk from CVE-2024-6838, a resource exhaustion vulnerability rated CVSS 5.3. Service availability could be impacted.

Is there a public PoC exploit available for CVE-2024-6838?

Yes, a public proof-of-concept exploit is available for CVE-2024-6838. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate CVE-2024-6838?

Within 30 days: Identify affected systems running mlflow/mlflow and apply vendor patches as part of regular patch cycle. Monitor vendor channels for patch availability.

Mlflow CVE-2024-6838

MEDIUM

Uncontrolled Resource Consumption (CWE-400)

2025-03-20 security@huntr.dev

Denial Of Service Mlflow AI / ML

5.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.3 MEDIUM

AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

Low

Lifecycle Timeline

Analysis Generated

Mar 28, 2026 - 18:32 vuln.today

PoC Detected

Apr 01, 2025 - 20:33 vuln.today

Public exploit code

CVE Published

Mar 20, 2025 - 10:15 nvd

MEDIUM 5.3

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

1 pypi packages depend on mlflow (1 direct, 0 indirect)

Ecosystem-wide dependent count for version 2.13.2.

DescriptionCVE.org

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.

AnalysisAI

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. Rated medium severity (CVSS 5.3), this vulnerability is remotely exploitable, no authentication required, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as Uncontrolled Resource Consumption (CWE-400), which allows attackers to cause denial of service by exhausting system resources. 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. Affected products include: Lfprojects Mlflow.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Implement rate limiting, set resource quotas, validate input sizes, use timeouts.

CVE-2024-6838 vulnerability details – vuln.today

Back

Mlflow CVE-2024-6838

Severity by source

CVSS VectorNVD

Lifecycle Timeline

Blast Radius

DescriptionCVE.org

AnalysisAI

Technical ContextAI

RemediationAI

Share

External POC / Exploit Code