Patchfirst
CVE-2023-1177 Public exploit Critical · 9.3 EPSS 69.7%

Path Traversal: '\..\filename' in mlflow/mlflow

mlflow · mlflow/mlflow

Summary

The path traversal flaw affects the mlflow/mlflow repository (the MLflow project) in versions prior to 2.2.1, where file paths containing backslash-based parent-directory sequences ("\..\filename") are not properly restricted. An attacker with network access can exploit it without authentication or user interaction, provided the vulnerable component is reachable, to access files outside the intended directory.

Official description · CVE.org

Path Traversal: '\..\filename' in GitHub repository mlflow/mlflow prior to 2.2.1.

Breakdown
66.4 / 100
Exploited
Yes, in VulnCheck KEV
Reports
0
Tactics
0/15

First seen exploited 8 months after disclosure. Public exploit code (PoC-in-GitHub) appeared 8 months after disclosure.

  1. Disclosedday 0
  2. Public exploit codePoC-in-GitHub+8 mo
  3. First seen exploitedVulnCheck KEV evidence+8 mo

techniques

No techniques linked

No ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.

Am I affected? What do I upgrade to?

From GitHub Security Advisories and OSV

1 package in 1 ecosystem. Main package: mlflow.

Upgrade to 2.22.4

Fixes this CVE and 5 other known vulnerabilities in this package (CVE-2023-2356, CVE-2023-3765, +3).

Still affected on this line by CVE-2026-2614 (fixed in 3.10.0, a newer line); CVE-2026-2652 (fixed in 3.10.0, a newer line); CVE-2026-64849 (fixed in 3.15.0, a newer line).

pippip install "mlflow>=2.22.4"

First fixed in 2.2.1 for CVE-2023-1177.

Affected versions

If you runUpgrade to
All versions before 2.2.12.22.4first fix for this CVE: 2.2.1

“Up to” means the second version is the fix and is not affected.

Check your lockfile against all CVEs

What security researchers reported

Not named in any threat report yet

References

2 links, grouped by NVD tag
↑ ↓ chooseEnter openEsc close