# CVE-2026-127202: MLflow < 3.18.0 Path Traversal via model_id in log_outputs API

> Unauthenticated attackers can write files and directories anywhere on MLflow servers using the FileStore backend via a crafted model_id.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 12 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-2265-6gg9-3q46

## What is CVE-2026-127202?

CVE-2026-127202 is a medium-severity path traversal vulnerability in mlflow, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-127202?

1 open source package ship an affected version, including mlflow.

An affected version is exposed as installed. No special setting or call is needed.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `mlflow` | PyPI | `pkg:pypi/mlflow` | All versions | 3.18.0 |

## How do I fix CVE-2026-127202?

Upgrade mlflow to 3.18.0 or later.

## Is CVE-2026-127202 being exploited?

There is no known exploitation of CVE-2026-127202 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-127202 and fix it if it is affected.

What it is: CVE-2026-127202 is a medium-severity path traversal vulnerability in mlflow, published on 12 Nov 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-127202 in the wild and no public exploit code.
Exposure: An affected version is exposed as installed. No special setting or call is needed.

Affected packages and fixed versions:
- mlflow (PyPI): affected all versions; fixed in 3.18.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-127202/ (Markdown: https://insights.sbomify.com/CVE-2026-127202/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-127202
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-127202
- OSV: https://osv.dev/vulnerability/CVE-2026-127202

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-127202/
Summaries are generated and may contain mistakes; the official description above is the record.
