MLflow Unrestricted Experiment Name Length Vulnerability Leading to Denial-of-Service

Vulnerability

A denial-of-service vulnerability has been identified in MLflow version 2.13.2. The issue arises from the absence of a limit on the length of experiment names, allowing users to create or rename experiments with an excessive number of integers. This can cause the MLflow user interface to become unresponsive, disrupting workflows and degrading the overall user experience. Additionally, there is no character limit for the 'artifact_location' parameter when creating an experiment, which could potentially be exploited in a similar manner.

Impact

Exploiting this vulnerability causes the MLflow UI to freeze, leading to a denial-of-service condition that disrupts users' ability to manage and track experiments. This issue can be particularly problematic in collaborative environments where MLflow is essential for experiment management.

Reproduction

To reproduce this vulnerability, create or rename an experiment in MLflow 2.13.2, using a name that contains a large number of integers. There is no limit to the number of integers that can be used, but using over 95 million integers has been tested and confirmed to cause the issue. After renaming the experiment, refresh the MLflow UI page to observe the unresponsiveness.

Added: Jun 9, 2025, 7:46 PM
Updated: Jun 9, 2025, 7:46 PM

Vulnerability Rating

Custom Algorithm
spread
5.7
impact
2.5
exploitability
9.1
remediation
0.0
relevance
0.0
threat
6.4
urgency
2.9
incentive
10.0

Our algorithm analyzes dozens of metrics to generate these 8 key vulnerability categories, which are then combined to calculate the overall risk score.