Patchfirst
CVE-2023-6909 Public exploit High · 7.5 EPSS 89.7%

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

mlflow · mlflow/mlflow

Summary

The path traversal flaw lies in the mlflow/mlflow GitHub repository, in its handling of filenames containing '\..\' sequences, in versions prior to 2.9.2. An attacker with network access and no authentication or user interaction could exploit this to read data beyond the intended directory, with the impact limited to confidentiality.

Official description · CVE.org

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

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

First seen exploited 2 years after disclosure.

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

2 related vulnerabilities in the same code over 4 months.

Linked vulnerabilitiesLinked by evidence that a fix failed or the same code was patched again. Oldest first.

  1. This CVECVE-2023-6909Path Traversal: '\..\filename' in mlflow/mlflow18 Dec 2023
  2. relatedLow

    Why these are linked:

    • Stated in the CVE textThis issue is similar to CVE-2023-6909 but utilizes a different component of the URI to achieve the same effect.
    CVE-2024-1594Local File Read via Path Traversal in mlflow/mlflow16 Apr 2024

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-2356, +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.9.2 for CVE-2023-6909.

Affected versions

If you runUpgrade to
All versions before 2.9.22.22.4first fix for this CVE: 2.9.2

“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