Quick answers
- Is CVE-2026-0545 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-0545 being exploited in the wild.
- How severe is CVE-2026-0545?
- Critical severity, with a CVSS score of 9.8, published 3 April 2026.
- Which products and versions are affected?
- mlflow (PyPI) ECOSYSTEM:introduced=0,last_affected=3.10.1.
- Is there a fix for CVE-2026-0545?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-0545 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-0545?
- Check whether you run mlflow (PyPI) at an affected version. 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.
Technical details
A vulnerability exists in MLflow's FastAPI implementation where endpoints under `/ajax-api/3.0/jobs/*` fail to enforce authentication or authorization checks even when `basic-auth` is enabled. If the server is configured with `MLFLOW_SERVER_ENABLE_JOB_EXECUTION=true` and has allowlisted job functions, an unauthenticated remote attacker can submit, read, search, or cancel jobs. This bypass can lead to Remote Code Execution (RCE) if the allowlisted jobs perform privileged operations like shell execution. It also facilitates Denial of Service (DoS) through job spamming and unauthorized data exposure.
Affected products
- MLflow MLflow latest
- Red Hat Red Hat OpenShift AI (RHOAI)
Identifiers
- CVE-2026-0545
- GHSA-7qhf-v65m-g5f3
- PYSEC-2026-419
Timeline
- 2026-04-03: disclosed
- 2026-04-03: advisory