CVE-2022-0736

Public Exploit
Insecure Temporary File in mlflow/mlflow

Description

Insecure Temporary File in GitHub repository mlflow/mlflow prior to 1.23.1.

Category

7.5
CVSS
Severity: High
CVSS 3.1 •
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.60%
Third-Party Advisory github.com Third-Party Advisory huntr.dev
Affected: mlflow mlflow/mlflow
Published at:
Updated at:

References

Link Tags
https://huntr.dev/bounties/e5384764-c583-4dec-a1d8-4697f4e12f75 exploit third party advisory patch
https://github.com/mlflow/mlflow/commit/61984e6843d2e59235d82a580c529920cd8f3711 third party advisory patch

Frequently Asked Questions

What is the severity of CVE-2022-0736?
CVE-2022-0736 has been scored as a high severity vulnerability.
How to fix CVE-2022-0736?
To fix CVE-2022-0736, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2022-0736 being actively exploited in the wild?
It is possible that CVE-2022-0736 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2022-0736?
CVE-2022-0736 affects mlflow mlflow/mlflow.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.