CVE-2026-127202mlflow path traversal
CVE-2026-127202 is a path traversal in mlflow, rated medium (6.3 on CVSS 4.0).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Awaiting Analysis
What it is
A file name from the request can climb out of the intended folder with sequences like ../, reaching files the service never meant to expose.
How it is reached
An attacker can exploit it over the network, without an account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.
What an attacker gains
The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker read or write files outside the folders the service meant to expose.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade mlflow to 3.18.0 or later.
- Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
Description from NVD
MLflow before 3.18.0 using the FileStore backend contains a path traversal vulnerability that allows unauthenticated remote attackers to write files outside the intended run directory by supplying a malicious model_id parameter to the log outputs API. Attackers can exploit the unvalidated model_id containing ../ sequences via the POST /api/3.0/mlflow/runs/outputs endpoint to create directories and write a meta.yaml file at arbitrary filesystem locations, limited only by the server account's permissions. FileStore was the default backend before 3.7.0 and is opt-in afterward through MLFLOW_ALLOW_FILE_STORE.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- File storage the service can read or write. The flaw sits between the application and the file system it can reach.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- Between the application and the file system it can reach. An attacker who crosses it can read or write files outside the folders the service meant to expose.
Questions to answer about your own systems
- Where does mlflow run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.