CVE-2026-127202

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-11-12 16:30 UTC ReservedThe CVE id was reserved by its CNA
2. 2026-11-12 17:17 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-11-12 17:17 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: not scored yet.
• Severity: 6.3 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-11-12 17:17 UTC

Last modified

2026-11-12 17:17 UTC

Weakness

CWE-22 · Path traversal

Record status

Awaiting Analysis

Attack profile CVSS 4.0 · 6.3

Attack vector

Network

Complexity

Low

Attack requirements

Present

Privileges needed

None

User interaction

None

Confidentiality

None

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-127202.md and follow it. Check whether this project is affected by CVE-2026-127202. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge