CVE-2026-127202

Description

A flaw was found in MLflow when using the FileStore backend. An unauthenticated remote attacker can exploit a path traversal vulnerability by submitting directory traversal sequences in the model identifier parameter to the log outputs application programming interface (API). Successful exploitation allows the attacker to create directories and write files outside the intended storage location on the server filesystem, restricted only by the permissions of the application process.

Statement

This vulnerability is rated as Moderate severity because, although unauthenticated remote attackers can invoke the path traversal flaw, the operational impact is confined to creating directories and writing structured metadata files within the local privileges of the running service account. Red Hat deployments typically leverage relational database or object storage backends rather than the legacy FileStore, which requires explicit opt-in enablement in current releases. Because attackers cannot inject arbitrary code or extract file contents through this mechanism, overall system confidentiality and availability are preserved.

Mitigation

Disable the legacy FileStore backend and restrict access to the MLflow tracking service.

1. Avoid the FileStore backend:
Ensure the `MLFLOW_ALLOW_FILE_STORE` environment variable is unset in the MLflow server execution environment:

unset MLFLOW_ALLOW_FILE_STORE
Configure the tracking server with an alternative supported backend, such as a relational database store using the `--backend-store-uri` option.

2. Restrict network reachability:
Limit network access to the MLflow service port (default TCP 5000) to authorized hosts using firewalld:

firewall-cmd --permanent --remove-port=5000/tcp
firewall-cmd --permanent --zone=trusted --add-source=<TRUSTED_IP_RANGE>
firewall-cmd --reload

Caveats:
Migrating to a database backend requires moving existing experiment data and tracking metadata. Modifying service configurations requires restarting the MLflow daemon, and reloading firewall rules will temporarily disrupt existing network sessions.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score5.3N/A5.3
Attack VectorNetworkN/ANetwork
Attack ComplexityLowN/ALow
Privileges RequiredNoneN/ANone
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityNoneN/ANone
Integrity ImpactLowN/ALow
Availability ImpactNoneN/ANone

Vector

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

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

Understanding the Weakness (CWE)

Integrity,Confidentiality,Availability

Technical Impact: Execute Unauthorized Code or Commands

The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.

Integrity

Technical Impact: Modify Files or Directories

The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow an attacker to bypass authentication.

Confidentiality

Technical Impact: Read Files or Directories

The attacker may be able to read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing attacks in order to break into an account on the system.

Availability

Technical Impact: DoS: Crash, Exit, or Restart

The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.

Frequently Asked Questions

Want to get errata notifications? Sign up here.