| Server-Side Request Forgery in the MLflow tracking server via client-supplied artifact locations and model version sourcesCVE-2026-118628 | High | < 3.18.0 | 3.18.0 | 2026-11-13 |
| Missing authorization on gateway secret creation in MLflow basic-auth with workspaces enabledGHSA-4449-4cjp-ffp5 | Medium | >= 3.10.0, < 3.17.0 | 3.17.0 | 2026-10-28 |
| MLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacCVE-2026-116692 | Critical | >= 3.12.0rc0, < 3.17.0 | 3.17.0 | 2026-10-27 |
| MLflow CrewAI autologging records LLM provider API keys in logged trace spansCVE-2026-116691 | Medium | >= 2.19.0, < 3.17.0 | 3.17.0 | 2026-10-27 |
| MLflow vulnerable to arbitrary file read on unauthenticated servers via prompt model version sourceCVE-2026-116690 | High | >= 3.10.0, < 3.17.0 | 3.17.0 | 2026-10-27 |
| MLflow: SSRF on unauthenticated MLflow servers via third-party scorer kwargs in the scorer invoke, register, and GenAI evaluate endpointsCVE-2026-115886 | Medium | >= 3.12.0rc0, < 3.17.0 | 3.17.0 | 2026-10-23 |
| MLflow FileStore trace IDs allow path traversal and arbitrary file writesCVE-2026-53995 | High | <= 3.17.1 | 3.17.2 | 2026-10-20 |
| MLFLOW_ALLOW_PICKLE_DESERIALIZATION=False safety control bypassed by mlflow.statsmodels flavor — RCE via crafted model artifactGHSA-gqvg-gmmx-x4hm | High | >= 2.1.0, < 3.15.0 | 3.15.0 | 2026-09-01 |
| MLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebindingCVE-2026-64849Exploited in the wild | Critical | >= 3.3.0, < 3.15.0 | 3.15.0 | 2026-08-17 |
| MLflow AI Gateway permits SSRF through an unvalidated api_baseCVE-2026-71211 | High | >= 3.13.0, <= 3.15.2 | No fix yet | 2026-08-05 |
| LogInputs endpoint bypasses per-run UPDATE authorization in MLflow basic-authCVE-2026-69146 | Medium | < 3.16.0 | 3.16.0 | 2026-08-04 |
| CreateModelVersion source validation does not check READ permission on referenced run_idCVE-2026-69148 | Medium | < 3.15.0 | 3.15.0 | 2026-08-04 |
| MLflow: trace API endpoints lack proper authorization validatorsCVE-2026-8147 | High | >= 2.14.0rc0, < 3.13.0rc0 | 3.13.0rc0 | 2026-07-02 |
| MLflow: Deterministic sampling in dataset digest enables predictable collisionsCVE-2026-10803 | Low | < 3.10.1 | 3.10.1 | 2026-06-04 |
| MLflow: Environment variable injection in AI Gateway secrets enables server-side credential exfiltrationCVE-2026-4035 | Critical | < 3.11.0 | 3.11.0 | 2026-06-03 |
| MLflow: Any authenticated user can enumerate all gateway secrets, endpoints, and model definitionsCVE-2026-3198 | Medium | < 3.11.0rc0 | 3.11.0rc0 | 2026-06-02 |
| MLflow allows unauthorized access to multipart upload endpoints when the `--serve-artifacts` mode is enabledCVE-2026-2651 | Critical | < 3.10.0 | 3.10.0 | 2026-05-26 |
| MLflow authenticated users can enumerate any registered model versions due to lack of per-model permissions checksCVE-2026-2734 | Medium | < 3.10.0 | 3.10.0 | 2026-05-21 |
| MLflow: Improper Origin Validation in MLflow Assistant /ajax-api Endpoints Enables Browser-Mediated Local Command ExecutionCVE-2026-2611 | Critical | = 3.9.0 | 3.10.0 | 2026-05-19 |
| MLFlow Creates a Temporary File With Insecure PermissionsCVE-2026-4137 | High | >= 1.26.0, < 3.11.0 | 3.11.0 | 2026-05-18 |
| MLflow: unauthenticated access to certain FastAPI routesCVE-2026-2652 | High | < 3.11.0 | 3.11.0 | 2026-05-15 |
| MLflow allows an unauthenticated remote attacker to read arbitrary files from the server's filesystemCVE-2026-2614 | High | < 3.10.0 | 3.10.0 | 2026-05-11 |
| MLflow Has a Server-Side Request Forgery (SSRF) VulnerabilityCVE-2026-2393 | High | < 3.9.0 | 3.9.0 | 2026-05-11 |
| MLflow is vulnerable to an authorization bypass affecting the AJAX endpointCVE-2026-33866 | Medium | <= 3.10.1 | 3.11.0rc0 | 2026-04-07 |
| MLflow is vulnerable to Stored Cross-Site Scripting (XSS) caused by unsafe parsing of YAML-based MLmodel artifacts in its web interfaceCVE-2026-33865 | Medium | <= 3.10.1 | 3.11.1 | 2026-04-07 |
| mlflow: FastAPI job endpoints under `/ajax-api/3.0/jobs/*` are not protected by authentication or authorizationCVE-2026-0545 | Critical | <= 3.10.1 | No fix yet | 2026-04-03 |
| Mlflow: Command Injection when serving models with enable_mlserver=TrueCVE-2026-0596 | Critical | < 3.9.0 | 3.9.0 | 2026-03-31 |
| MLflow Command Injection vulnerabilityCVE-2025-15379 | Critical | < 3.8.1 | 3.8.1 | 2026-03-30 |
| MLFlow path traversal vulnerabilityCVE-2025-15036 | Critical | < 3.9.0rc0 | 3.9.0rc0 | 2026-03-30 |
| MLFlow allows Tracing + Assessments AccessCVE-2025-15381 | High | <= 3.8.1 | No fix yet | 2026-03-27 |
| Arbitrary file write via tar traversal in mlflowCVE-2025-15031 | High | < 3.9.0rc0 | 3.9.0rc0 | 2026-03-19 |
| MLflow has a command injection in mlflow/sagemaker/__init__.pyCVE-2025-14287 | High | < 3.8.0rc0 | 3.8.0rc0 | 2026-03-16 |
| MLflow Use of Default Password Authentication Bypass VulnerabilityCVE-2026-2635 | Critical | < 3.8.0rc0 | 3.8.0rc0 | 2026-02-21 |
| MLflow Tracking Server Artifact Handler Directory Traversal Remote Code Execution VulnerabilityCVE-2026-2033 | High | < 3.8.0rc0 | 3.8.0rc0 | 2026-02-21 |
| mlflow Creates of Temporary File in Directory with Insecure PermissionsCVE-2025-10279 | High | < 3.4.0rc0 | 3.4.0rc0 | 2026-02-02 |
| MLFlow is vulnerable to DNS rebinding attacks due to a lack of Origin header validationCVE-2025-14279 | High | < 3.5.0 | 3.5.0 | 2026-01-12 |
| MLflow Tracking Server Model Creation Directory Traversal Remote Code Execution VulnerabilityCVE-2025-11201 | High | < 2.22.4 | 2.22.4 | 2025-10-29 |
| MLflow Tracking Server Model Creation Directory Traversal Remote Code Execution VulnerabilityCVE-2025-11201 | High | >= 3.0.0rc0, < 3.0.0 | 3.0.0 | 2025-10-29 |
| MLflow Weak Password Requirements Authentication Bypass VulnerabilityCVE-2025-11200 | High | < 2.22.0rc0 | 2.22.0rc0 | 2025-10-29 |
| MLFlow SSRF via gateway_proxy_handlerCVE-2025-52967 | Medium | < 2.22.2 | 2.22.2 | 2025-06-23 |
| MLFlow SSRF via gateway_proxy_handlerCVE-2025-52967 | Medium | >= 3.0.0rc0, < 3.1.0 | 3.1.0 | 2025-06-23 |
| MLflow Uncontrolled Resource Consumption vulnerabilityCVE-2025-0453 | Medium | <= 2.17.2 | No fix yet | 2025-03-20 |
| MLflow has Weak Password RequirementsCVE-2025-1474 | Low | < 2.19.0 | 2.19.0 | 2025-03-20 |
| MLflow has a Local File Read/Path Traversal in dbfsCVE-2024-8859 | High | < 2.17.0rc0 | 2.17.0rc0 | 2025-03-20 |
| MLflow Cross-Site Request Forgery (CSRF) vulnerabilityCVE-2025-1473 | Medium | >= 2.17.0, < 2.20.3 | 2.20.3 | 2025-03-20 |
| MLflow Uncontrolled Resource Consumption vulnerabilityCVE-2024-6838 | Medium | <= 2.13.2 | No fix yet | 2025-03-20 |
| MLflow's excessive directory permissions allow local privilege escalationCVE-2024-27134 | High | < 2.16.0 | 2.16.0 | 2024-11-25 |
| Remote code execution in mlflowCVE-2024-0520 | Critical | < 2.9.0 | 2.9.0 | 2024-06-06 |
| Undefined Behavior in mlflowCVE-2024-3099 | Medium | < 2.11.3 | 2.11.3 | 2024-06-06 |
| Local File Inclusion in mlflowCVE-2024-2928 | High | < 2.11.3 | 2.11.3 | 2024-06-06 |
| MLFlow unsafe deserializationCVE-2024-37053 | High | >= 1.1.0, <= 2.14.1 | No fix yet | 2024-06-04 |
| MLFlow unsafe deserializationCVE-2024-37052 | High | >= 1.1.0, <= 2.14.1 | No fix yet | 2024-06-04 |
| MLFlow unsafe deserializationCVE-2024-37056 | High | >= 1.23.0, <= 2.14.1 | No fix yet | 2024-06-04 |
| MLFlow unsafe deserializationCVE-2024-37060 | High | >= 1.27.0, <= 2.14.1 | No fix yet | 2024-06-04 |
| MLFlow unsafe deserializationCVE-2024-37058 | High | >= 2.5.0, <= 2.14.1 | No fix yet | 2024-06-04 |
| MLFlow unsafe deserializationCVE-2024-37054 | High | >= 0.9.0, <= 2.14.1 | No fix yet | 2024-06-04 |
| MLFlow unsafe deserializationCVE-2024-37057 | High | >= 2.0.0rc0, <= 2.14.1 | No fix yet | 2024-06-04 |
| MLFlow improper input validationCVE-2024-37061 | High | >= 1.11.0, <= 2.13.1 | No fix yet | 2024-06-04 |
| MLFlow unsafe deserializationCVE-2024-37059 | High | >= 0.5.0, <= 3.4.0 | No fix yet | 2024-06-04 |
| MLFlow unsafe deserializationCVE-2024-37055 | High | >= 1.24.0, <= 2.14.1 | No fix yet | 2024-06-04 |
| MLflow allows low privilege users to delete any artifactCVE-2024-4263 | Medium | < 2.10.1 | 2.10.1 | 2024-05-16 |
| MLflow has a Local File Read/Path Traversal bypassCVE-2024-3848 | High | >= 2.9.2, < 2.12.1 | 2.12.1 | 2024-05-16 |
| mlflow vulnerable to Path TraversalCVE-2024-1560 | High | <= 2.9.2 | No fix yet | 2024-04-16 |
| mlflow vulnerable to Path TraversalCVE-2024-1593 | High | <= 2.9.2 | No fix yet | 2024-04-16 |
| mlflow Path Traversal vulnerabilityCVE-2024-1483 | High | <= 2.9.2 | 2.12.1 | 2024-04-16 |
| mlflow vulnerable to Path TraversalCVE-2024-3573 | Critical | < 2.10.0 | 2.10.0 | 2024-04-16 |
| mlflow vulnerable to Path TraversalCVE-2024-1558 | High | <= 2.9.2 | 2.12.1 | 2024-04-16 |
| mlflow vulnerable to Path TraversalCVE-2024-1594 | High | <= 2.9.2 | No fix yet | 2024-04-16 |
| MLFlow Cross-site Scripting vulnerability leads to client-side Remote Code ExecutionCVE-2024-27133 | Critical | < 2.10.0 | 2.10.0 | 2024-02-24 |
| Cross-site Scripting in MLFlowCVE-2024-27132 | Critical | < 2.10.0 | 2.10.0 | 2024-02-24 |
| MLflow Server-Side Request Forgery (SSRF)CVE-2023-6974 | Critical | < 2.9.2 | 2.9.2 | 2023-12-20 |
| MLflow Path Traversal VulnerabilityCVE-2023-6909 | High | < 2.9.2 | 2.9.2 | 2023-12-20 |
| MLFlow Path Traversal VulnerabilityCVE-2023-6975 | Critical | < 2.9.2 | 2.9.2 | 2023-12-20 |
| MLflow Local File Disclosure VulnerabilityCVE-2023-6977 | High | < 2.9.2 | 2.9.2 | 2023-12-20 |
| MLflow Path Traversal VulnerabilityCVE-2023-6976 | High | < 2.9.2 | 2.9.2 | 2023-12-20 |
| mlflow Command Injection vulnerabilityCVE-2023-6940 | High | < 2.9.2 | 2.9.2 | 2023-12-19 |
| Path traversal in MLflowCVE-2023-6831 | Critical | < 2.9.2 | 2.9.2 | 2023-12-15 |
| Path traversal in MLflowCVE-2023-6753 | High | < 2.9.2 | 2.9.2 | 2023-12-13 |
| Jinja2 template injection in mlflowCVE-2023-6709 | High | < 2.9.2 | 2.9.2 | 2023-12-12 |
| Cross-site Scripting (XSS) in MLflowCVE-2023-6568 | Medium | < 2.9.0 | 2.9.0 | 2023-12-07 |
| Information exposure in MLflowCVE-2023-43472 | High | < 2.9.0 | 2.9.0 | 2023-12-05 |
| MLflow authentication requirement bypass can allow a user to arbitrarily create an accountCVE-2023-6014 | Critical | < 2.8.0 | 2.8.0 | 2023-11-16 |
| Remote Code Execution due to Full Controled File Write in mlflowCVE-2023-6018 | Critical | <= 2.8.1 | 2.9.2 | 2023-11-16 |
| MLflow allowed arbitrary files to be PUT onto the serverCVE-2023-6015 | Critical | < 2.8.1 | 2.8.1 | 2023-11-16 |
| mlflow vulnerable to OS Command InjectionCVE-2023-4033 | High | < 2.6.0 | 2.6.0 | 2023-08-01 |
| MLflow Path Traversal vulnerabilityCVE-2023-3765 | Critical | < 2.5.0 | 2.5.0 | 2023-07-19 |
| mlflow Path Traversal vulnerabilityCVE-2023-2780 | Critical | < 2.3.0 | 2.3.0 | 2023-05-17 |
| mflow vulnerable to directory traversalCVE-2023-30172 | High | < 2.0.0rc0 | 2.0.0rc0 | 2023-05-11 |
| Remote file access vulnerability in `mlflow server` and `mlflow ui` CLIsGHSA-83fm-w79m-64r5 | Critical | < 2.3.1 | 2.3.1 | 2023-05-01 |
| Relative path traversal in mlflowCVE-2023-2356 | High | < 2.3.1 | 2.3.1 | 2023-04-28 |
| Remote file existence check vulnerability in `mlflow server` and `mlflow ui` CLIsCVE-2023-1176 | Medium | <= 2.2.0 | 2.2.1 | 2023-03-24 |
| mlflow is vulnerable to remote file access in `mlflow server` and `mlflow ui` CLIsCVE-2023-1177 | Critical | <= 2.2.0 | 2.2.1 | 2023-03-24 |
| Insecure Temporary File in mlflowCVE-2022-0736 | High | < 1.23.1 | 1.23.1 | 2022-02-24 |