Patchfirst
CVE-2023-2356 Public exploit Critical · 10.0 EPSS 4.2%

Relative Path Traversal in mlflow/mlflow

mlflow · mlflow/mlflow

Summary

A relative path traversal flaw exists in the mlflow/mlflow repository, the MLflow project's codebase, in versions prior to 2.3.1. An attacker can exploit this weakness by supplying crafted relative paths that escape the intended directory; the attack vector indicates it is reachable over the network, requires no privileges and no user interaction, and has low complexity.

Official description · CVE.org

Relative Path Traversal in GitHub repository mlflow/mlflow prior to 2.3.1.

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

First seen exploited 4 years after disclosure.

  1. Disclosedday 0
  2. First seen exploitedVulnCheck KEV evidence+4 yrs

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-1177, 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.3.1 for CVE-2023-2356.

Affected versions

If you runUpgrade to
All versions before 2.3.12.22.4first fix for this CVE: 2.3.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