# CVE-2026-0545: Missing Authentication for Critical Function in mlflow/mlflow

> Unauthenticated attackers can execute jobs in MLflow when basic-auth is enabled, potentially leading to remote code execution or denial of service.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-7qhf-v65m-g5f3, MINI-54gx-rj97-rrc8, PYSEC-2026-419

## What is CVE-2026-0545?

CVE-2026-0545 is a critical missing authorization vulnerability in Lfprojects Mlflow, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In mlflow/mlflow, the FastAPI job endpoints under `/ajax-api/3.0/jobs/*` are not protected by authentication or authorization when the `basic-auth` app is enabled. This vulnerability affects the latest version of the repository. If job execution is enabled (`MLFLOW_SERVER_ENABLE_JOB_EXECUTION=true`) and any job function is allowlisted, any network client can submit, read, search, and cancel jobs without credentials, bypassing basic-auth entirely. This can lead to unauthenticated remote code execution if allowed jobs perform privileged actions such as shell execution or filesystem changes. Even if jobs are deemed safe, this still constitutes an authentication bypass, potentially resulting in job spam, denial of service (DoS), or data exposure in job results.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-0545?

3 open source packages ship an affected version, including mlflow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mlflow` | PyPI | All versions to 3.10.1 | None |
| `mlflow` | PyPI | All versions to 3.10.1 | None |
| `mlflow` | PyPI | All versions to 3.10.1 | None |

Products: Lfprojects Mlflow.

## How do I fix CVE-2026-0545?

No fix has been published for CVE-2026-0545 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-0545 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0545 exists.

Public exploit code:

- MLflow Job API - Authentication Bypass (nuclei): http/cves/2026/CVE-2026-0545.yaml

## Other vulnerabilities in Lfprojects Mlflow

- [CVE-2026-64849](https://insights.sbomify.com/CVE-2026-64849/): MLflow Server-Side Request Forgery (critical 9.3, exploited in the wild)
- [CVE-2025-15379](https://insights.sbomify.com/CVE-2025-15379/): Command Injection in mlflow/mlflow (critical 10.0)
- [CVE-2024-0520](https://insights.sbomify.com/CVE-2024-0520/): Remote Code Execution due to Full Controlled File Write in mlflow/mlflow (critical 10.0)
- [CVE-2023-6977](https://insights.sbomify.com/CVE-2023-6977/): Path Traversal: '\..\filename' (critical 10.0)
- [CVE-2023-6709](https://insights.sbomify.com/CVE-2023-6709/): Improper Neutralization of Special Elements Used in a Template Engine in mlflow/mlflow (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-0545 and fix it if it is affected.

What it is: CVE-2026-0545 is a critical missing authorization vulnerability in Lfprojects Mlflow, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-0545 exists.

Affected packages and fixed versions:
- mlflow (PyPI): affected all versions up to 3.10.1; no fix listed
- mlflow (PyPI): affected all versions up to 3.10.1; no fix listed
- mlflow (PyPI): affected all versions up to 3.10.1; no fix listed

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-2026-0545/ (Markdown: https://insights.sbomify.com/CVE-2026-0545/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-0545
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-0545
- OSV: https://osv.dev/vulnerability/CVE-2026-0545

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-0545/
Summaries are generated and may contain mistakes; the official description above is the record.