Skip to content
Fencer Intel
high 8.2

CVE-2022-0736 json

Insecure Temporary File in mlflow/mlflow

published 4y ago modified 2mo ago also BIT-mlflow-2022-0736 , EUVD-2022-0158 , GHSA-vqj2-4v8m-8vrq , PYSEC-2022-28

cvss
8.2
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.6%
EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits
0
none known

Summary

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

Patch / fix

  • pypi mlflow 1.23.1
  • bitnami mlflow 1.23.1
  • mlflow mlflow/mlflow 1.23.1

Is CVE-2022-0736 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.58% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/e5384764-c583-4dec-a1d8-4697f4e12f75 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 8.2 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
GitHub 3.0 8.2 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi mlflow
<1.23.1
1.23.1
bitnami mlflow
<1.23.1
1.23.1

Affected products

  • mlflow mlflow/mlflow

Classification

Weakness
  • CWE-377 DEPRECATED: Insecure Temporary File
  • CWE-668 Exposure of Resource to Wrong Sphere

References

Sources

Fencer Intel 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.