Skip to main content
VulnerabilityPublished Updated

CVE-2026-0545: mlflow/mlflow · Missing Authentication

Affects mlflow/mlflowSource CVE Database V5

0
Compare

Not known to be exploited · public detection template (Nuclei) · CVSS 9.1 Critical.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.0 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
4.3% chance of exploitation in 30 days – higher than 91% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Apr 2026

  2. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
mlflowmlflow/mlflowAffected
  • ≥ unspecified, ≤ latest
Fixed in–
PyPImlflowpkg:pypi/mlflowOther threatsAffected
  • *
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until an official fix is available, it is recommended to disable job execution (set MLFLOW_SERVER_ENABLE_JOB_EXECUTION=false) if not required, or restrict network access to the affected endpoints to trusted clients only. Review and limit allowlisted jobs to those that do not perform privileged actions. Monitor vendor advisories for updates and official patches.

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.

References

Community reviews

Loading reviews…