CVE-2022-0736 Insecure Temporary File in mlflow/mlflow
High 8.2
Published
Updated
Check this codebase for CVE-2022-0736 and fix it if it is affected.
What it is: CVE-2022-0736 is a high-severity vulnerability in Lfprojects Mlflow, published on 23 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0736 in the wild and no public exploit code.
Affected packages and fixed versions:
- mlflow (Bitnami): affected all versions; fixed in 1.23.1
- mlflow (PyPI): affected all versions; fixed in 1.23.1
- mlflow (PyPI): affected all versions; fixed in 1.23.1
- mlflow (PyPI): affected all versions; fixed in 1.23.1
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2022-0736/ (Markdown: https://insights.sbomify.com/CVE-2022-0736/index.md)
An insecure temporary file vulnerability in MLflow allows attackers to read or modify sensitive data during execution.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-0736?
CVE-2022-0736 is a high-severity vulnerability in Lfprojects Mlflow, published on 23 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Insecure Temporary File in GitHub repository mlflow/mlflow prior to 1.23.1.
Weakness: CWE-377
Which versions are affected by CVE-2022-0736?
4 open source packages ship an affected version, including mlflow. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
mlflow Bitnami | All versions | 1.23.1 |
mlflow PyPI | All versions | 1.23.1 |
mlflow PyPI | All versions | 1.23.1 |
mlflow PyPI | All versions | 1.23.1 |
Products include Lfprojects Mlflow.
How do I fix CVE-2022-0736?
Upgrade mlflow to 1.23.1 or later.
Is CVE-2022-0736 being exploited?
There is no known exploitation of CVE-2022-0736 in the wild and no public exploit code.
Other vulnerabilities in Lfprojects Mlflow
- CVE-2026-64849 MLflow Server-Side Request Forgery
- CVE-2025-15379 Command Injection in mlflow/mlflow
- CVE-2024-0520 Remote Code Execution due to Full Controlled File Write in mlflow/mlflow
- CVE-2023-6977 Path Traversal: '\..\filename'
- CVE-2023-6709 Improper Neutralization of Special Elements Used in a Template Engine in mlflow/mlflow
Sources
Also known as BIT-mlflow-2022-0736, GHSA-vqj2-4v8m-8vrq, PYSEC-2022-28.