# CVE-2026-118624: MLflow Tracking Server authorization bypass in Jobs API

Source: https://junglewise.ai/threats/cve-2026-118624-mlflow-tracking-server-jobs-missing-authorization-information  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-04. Updated: 2026-11-04  
License: CC BY 4.0 with a link back

CVE-2026-118624 · Severity: medium · CVSS 5.4 · Published 2026-11-04

MLflow Tracking Server is a platform for managing machine learning experiments and models. This vulnerability allows authenticated users to access sensitive information they should not have permission to view, such as details about other users' jobs or service account information, due to missing authorization checks in the Jobs API.

Technologies: [Mlflow](https://junglewise.ai/threats/technologies/mlflow-mlflow). Vendors: [MLflow](https://junglewise.ai/threats/vendors/mlflow).

## Quick answers

**Is CVE-2026-118624 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-118624 being exploited in the wild.

**How severe is CVE-2026-118624?** Medium severity, with a CVSS score of 5.4, published 4 November 2026.

**Which products and versions are affected?** MLflow MLflow.

**Is there a fix for CVE-2026-118624?** Yes: fixed in MLflow 3.16.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-118624 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-118624?** Check whether you run Mlflow. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in MLflow 3.16.0

## Technical details

The _find_validator function in MLflow Tracking Server lacks proper authorization checks, allowing authenticated attackers to access restricted functionality. The vulnerability requires prior authentication but permits disclosure of information in the context of the service account. An attacker can leverage this to read sensitive data they are not authorized to access.

## Affected products

- MLflow MLflow

## Timeline

- 2026-06-18: disclosed: Vulnerability reported to vendor
- 2026-10-29: advisory: Coordinated public release of advisory
- 2026-10-29: patched: Fix available in MLflow 3.16.0

## References

- [https://www.zerodayinitiative.com/advisories/ZDI-26-840/](https://www.zerodayinitiative.com/advisories/ZDI-26-840/)

## Related threats

- [MLflow path traversal in FileStore log outputs API](https://junglewise.ai/threats/cve-2026-127202-mlflow-before-3-18-0-using-the-filestore-backend-contains-a-path)
- [MLflow get-artifacts server-side request forgery information disclosure](https://junglewise.ai/threats/cve-2026-118628-mlflow-get-artifacts-server-side-request-forgery-information)
- [MLflow SHAP load_explainer deserialization of untrusted data](https://junglewise.ai/threats/cve-2026-118627-mlflow-shap-load-explainer-deserialization-of-untrusted-data)
- [MLflow Tracking Server missing authorization in get_endpoints](https://junglewise.ai/threats/cve-2026-118625-mlflow-tracking-server-missing-authorization-privilege)
- [MLflow PickleEvaluationArtifact deserialization of untrusted data](https://junglewise.ai/threats/cve-2026-118623-mlflow-pickleevaluationartifact-deserialization-of-untrusted)