dbcve.org
MlflowApplication · Lfprojects

CVE-2026-0545

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The FastAPI job endpoints under `/ajax-api/3.0/jobs/*` in MLflow bypass authentication when the basic-auth app is enabled, allowing any network client to submit, read, search, and cancel jobs without credentials if job execution is enabled and job functions are allowlisted. This enables unauthenticated remote code execution if allowlisted jobs perform privileged operations like shell commands or filesystem modifications.

MitigationConfigure authentication enforcement on all job endpoints or disable privileged job functions from the allowlist; consider disabling MLFLOW_SERVER_ENABLE_JOB_EXECUTION if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MlflowApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if MLflow job execution is enabled
    Inspect the environment variable MLFLOW_SERVER_ENABLE_JOB_EXECUTION or the MLflow configuration file for the setting 'enable_job_execution' or 'server_enable_job_execution'. If set to 'true' or '1', job execution is enabled.
    Affected if MLFLOW_SERVER_ENABLE_JOB_EXECUTION is set to true or the equivalent config option is enabled
  2. Check if job function allowlist is configured
    Inspect MLflow configuration for job function allowlisting. This may be an environment variable (such as MLFLOW_JOBS_ALLOWLIST or similar), a config file setting, or a database entry that defines which job functions are permitted to run.
    Affected if Job functions are allowlisted (any non-empty allowlist configuration exists)
  3. Verify basic-auth is configured for MLflow
    Check MLflow configuration for authentication settings. This typically involves checking for environment variables like MLFLOW_AUTH or basic-auth related configuration, or examining the mlflow configuration file for auth/backend settings.
    Affected if Basic-auth or any authentication mechanism is configured for the MLflow server
  4. Test unauthenticated access to job endpoints
    Send an HTTP request to the /ajax-api/3.0/jobs/* endpoints (such as GET /ajax-api/3.0/jobs or POST /ajax-api/3.0/jobs/submit) without providing any authentication credentials. Use curl or similar tool: curl -v http://<mlflow-host>:<port>/ajax-api/3.0/jobs/
    Affected if The job endpoints return successful responses (HTTP 2xx) without requiring authentication, indicating the authentication bypass is present

A user is affected if job execution is enabled with allowlisted job functions AND the /ajax-api/3.0/jobs/* endpoints are accessible without authentication even when basic-auth is configured for the MLflow server.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Configure authentication enforcement on all job endpoints or disable privileged job functions from the allowlist; consider disabling MLFLOW_SERVER_ENABLE_JOB_EXECUTION if not required.

Fix this in Mlflow Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0545 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0545 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data