S4E just found a high-severity finding from top 10 tcp port service scan
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
critical·Product Based Web Vulnerabilities·Updated May 5, 2026

CVE-2026-0545 Scanner

CVE-2026-0545 Scanner - Authentication Bypass vulnerability in MLflow

Est. Time~10 seconds
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
2.5k
Times Used
continuous scan runs
5.9k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2026-0545
9.8
CVSScritical
Exploitable remotely over the internet · no authentication required.

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.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
mlflow/mlflowby mlflow
unspecified
Red Hat OpenShift AI 3.4by Red Hat
AFFECTED< *SAFE ✓≥ *
Red Hat OpenShift AI 3.4by Red Hat
AFFECTED< *SAFE ✓≥ *
Red Hat OpenShift AI 3.4by Red Hat
AFFECTED< *SAFE ✓≥ *
Updated Aug 28, 2026View on NVD →
Detail

MLflow is a popular open-source platform used by data scientists and engineers for managing the machine learning lifecycle. It is widely adopted by organizations to streamline the tracking, reproduction, and deployment of machine learning models. MLflow provides functionalities, including tracking experiments, packaging code into reproducible runs, and sharing and deploying models. It integrates easily with existing tools and cloud infrastructure, making it a versatile choice for ML workflows. FastAPI is utilized within MLflow to handle HTTP requests to its Job API. Ensuring secure authentication of these requests is crucial to maintaining the integrity and confidentiality of managed jobs.

The authentication bypass vulnerability in MLflow allows unauthorized access to its Job API. This security flaw occurs due to unprotected endpoints when basic authentication is enabled. Attackers can exploit these endpoints to remotely submit and manage jobs without authentication. This exposes the system to severe risks, including unauthorized job execution and potential malicious activities. Addressing this vulnerability is critical to maintaining operational security within environments using MLflow.

The vulnerability detail reveals that MLflow's FastAPI job endpoints under "/ajax-api/3.0/jobs/*" lack proper authentication when basic authentication is enabled. This oversight leaves endpoints unprotected and accessible to unauthorized users. The vulnerable endpoints accept JSON requests intended for job management, including parameters for executing specified commands. Successful exploitation requires job execution to be enabled, allowing attackers to perform tasks typically restricted to authorized users. This type of vulnerability emphasizes the need for rigorous endpoint security practices.

If exploited, the authentication bypass could lead to significant negative impacts within affected systems. Unauthorized individuals can potentially gain control over job execution, leading to remote code execution or denial of service scenarios. Furthermore, unauthorized access could result in sensitive data exposure, risking confidentiality and potentially causing significant harm to the organization. Therefore, addressing this flaw is paramount to safeguarding system integrity and user data.

REFERENCES

Solution Advice
  • Apply the latest software updates for MLflow to ensure the latest security patches are in place.
  • Implement additional layers of security, such as IP whitelisting or network access control, to restrict access to critical API endpoints.
  • Review and strengthen the authentication mechanisms to protect against unauthorized access.
  • Regularly audit API endpoints to ensure compliance with security standards and identify potential vulnerabilities.
  • Consider integrating more robust authentication protocols beyond basic authentication.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

11,000+ scanners. Free to start. No credit card required.