CVE-2023-6975 json
Path Traversal: '\..\filename'
published 2023-12-20 2 y ago modified 2026-09-08 2 mo ago also BIT-mlflow-2023-6975 , EUVD-2023-3221 , GHSA-hh8p-p8mp-gqhm , PYSEC-2026-422
- cvss
- 9.8
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
A malicious user could use this issue to get command execution on the vulnerable machine and get access to data & models information.
Patch / fix
- pypi mlflow 2.9.2
- bitnami mlflow 2.9.2
- mlflow mlflow/mlflow 2.9.2
Exploit prediction
2.03% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.com https://huntr.com/bounties/029a3824-cee3-4cf1-b260-7138aa539b85 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.1 | 9.8 | CVSS:3.1/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.9.2 |
2.9.2 |
| bitnami | mlflow | <2.9.2 |
2.9.2 |
Affected products
- mlflow mlflow/mlflow
Classification
- Weakness
-
- CWE-29 Path Traversal: '\..\filename'
References
-
github.com
/mlflow/mlflow/commit/b9ab9ed77e1deda9697fe472fb1079fd428149ee
web, patch
-
huntr.com
/bounties/029a3824-cee3-4cf1-b260-7138aa539b85
web, exploit, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-6975
advisory, web
-
github.com
/mlflow/mlflow
package
-
pypi.org
/project/mlflow
package
-
github.com
/advisories/GHSA-hh8p-p8mp-gqhm
advisory
Sources
- CVE List CVE-2023-6975
- GitHub Advisory GHSA-hh8p-p8mp-gqhm
- NVD CVE-2023-6975
- OSV BIT-mlflow-2023-6975
- OSV PYSEC-2026-422
Fencer Vulns 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.