Skip to content
Fencer Intel
critical 9.8

CVE-2023-2780 json

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

published 3y ago modified 2mo ago also BIT-mlflow-2023-2780 , EUVD-2023-0159 , GHSA-wjq3-7jxx-whj9 , PYSEC-2023-69

cvss
9.8
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
6.3%
EPSS 6.3% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

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

Patch / fix

  • pypi mlflow 2.3.0, 2.3.1
  • bitnami mlflow 2.3.1
  • mlflow mlflow/mlflow 2.3.1

Is CVE-2023-2780 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

6.31% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-15).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/b12b0073-0bb0-4bd1-8fc2-ec7f17fd7689 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
pypi mlflow
<2.3.0
<2.3.1
2.3.0
2.3.1
bitnami mlflow
<2.3.1
2.3.1

Affected products

  • mlflow mlflow/mlflow

Classification

Weakness
  • CWE-29 Path Traversal: '\..\filename'

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.