CVE-2023-6018 in the critical feed json
MLflow Arbitrary File Write
published 2023-11-16 2 y ago modified 2026-07-13 3 mo ago also BIT-mlflow-2023-6018 , EUVD-2023-2888 , GHSA-5p3h-7fwh-92rc , PYSEC-2026-417
- cvss
- 10.0
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 47.9%
- EPSS 47.9% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
An attacker can overwrite any file on the server hosting MLflow without any authentication.
Patch / fix
Exploit prediction
47.87% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template Mlflow - Arbitrary File Write nuclei detection template
- huntr.com https://huntr.com/bounties/7cf918b5-43f4-48c0-a371-4d963ce69b30 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 10.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.0 | 10.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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.0 | 10.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | mlflow | <2.9.2 |
2.9.2 |
| bitnami | mlflow | — | no fix listed |
Affected products
- mlflow mlflow/mlflow
Classification
- Weakness
-
- CWE-78 Improper Neutralization of Special Elements used in an OS Command
References
-
github.com
/mlflow/mlflow/commit/55c72d02380e8db8118595a4fdae7879cb7ac5bd
web
-
huntr.com
/bounties/7cf918b5-43f4-48c0-a371-4d963ce69b30
web, exploit, technical-description, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2023-6018
advisory
-
github.com
/mlflow/mlflow
package
-
pypi.org
/project/mlflow
package
-
github.com
/advisories/GHSA-5p3h-7fwh-92rc
advisory
Sources
- CVE List CVE-2023-6018
- GitHub Advisory GHSA-5p3h-7fwh-92rc
- NVD CVE-2023-6018
- OSV BIT-mlflow-2023-6018
- OSV PYSEC-2026-417
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.