CVE-2023-4033 json
OS Command Injection in mlflow/mlflow
published 2023-08-01 3 y ago modified 2026-09-08 2 mo ago also BIT-mlflow-2023-4033 , EUVD-2023-0161 , GHSA-ffw3-6378-cqgp , PYSEC-2023-280
- cvss
- 8.8
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 69%
- public exploits
- 0
- none known
Summary
OS Command Injection in GitHub repository mlflow/mlflow prior to 2.6.0.
Patch / fix
- pypi mlflow 2.6.0
- bitnami mlflow 2.6.0
- mlflow mlflow/mlflow 2.6.0
- mlflow mlflow 2.6.0
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
1.24% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 8.8 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| GitHub | 3.0 | 8.8 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | mlflow | <2.6.0 |
2.6.0 |
| bitnami | mlflow | <2.6.0 |
2.6.0 |
Affected products
- mlflow mlflow/mlflow
- mlflow mlflow
Classification
- Weakness
-
- CWE-78 Improper Neutralization of Special Elements used in an OS Command
References
-
github.com
/mlflow/mlflow/commit/6dde93758d42455cb90ef324407919ed67668b9b
web, patch
-
huntr.dev
/bounties/5312d6f8-67a5-4607-bd47-5e19966fa321
web, permissions-required
-
nvd.nist.gov
/vuln/detail/CVE-2023-4033
advisory, web
-
github.com
/mlflow/mlflow
package
-
github.com
/pypa/advisory-database/tree/main/vulns/mlflow/PYSEC-2023-280.yaml
web
-
github.com
/advisories/GHSA-ffw3-6378-cqgp
advisory
Sources
- CVE List CVE-2023-4033
- GitHub Advisory GHSA-ffw3-6378-cqgp
- NVD CVE-2023-4033
- OSV BIT-mlflow-2023-4033
- OSV PYSEC-2023-280
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.