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

Published Mar 20, 2025
·
Updated

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 artifactlocation parameter while creating the experiment.

Affected Software

3 affected components
MLflow MLflow
pip/mlflow<=2.13.2
Lfprojects Mlflow=2.13.2

Event History

Mar 20, 2025
CVE Published
via MITRE·10:09 AM
Data Sourced
via MITRE·10:09 AM
DescriptionSeverityWeakness
Advisory Published
via GitHub·12:32 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-6838?

CVE-2024-6838 is considered a moderate severity vulnerability due to its potential to cause unresponsiveness in the MLflow UI.

2

How do I fix CVE-2024-6838?

To fix CVE-2024-6838, implement a limit on the number of integers allowed in experiment names in MLflow version 2.13.2 or earlier.

3

Which versions are affected by CVE-2024-6838?

CVE-2024-6838 affects MLflow version 2.13.2 and earlier.

4

What type of vulnerability is CVE-2024-6838?

CVE-2024-6838 is a design flaw that allows for the creation or renaming of experiments without a limit on the name length.

5

What impact does CVE-2024-6838 have on users?

The impact of CVE-2024-6838 is that it can cause the MLflow UI to become unresponsive when specific conditions are met.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203