Black Friday60% off BLACKFRIDAY2026
PlatformPlansPartners
Resources
ToolsBlogDocs
Sign Up →
medium·Product Based Web Vulnerabilities·Updated Nov 9, 2026

CVE-2026-115886 Scanner

CVE-2026-115886 Scanner - Server-Side-Request-Forgery (SSRF) vulnerability in MLflow

Est. Time~1 minutes
Scan TypeSingle Scan
Targetsdomain, subdomain, ipv4
CostFree
5
Times Used
continuous scan runs
4.2k
Continuously Checked
assets under CS
0
Vulnerabilities Found
confirmed findings
References
6.5
CVSSmedium
Exploitable remotely over the internet · no authentication required.
Description

MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. From 3.12.0rc0 until 3.17.0, the scorer invoke, register, and GenAI evaluate endpoints, including unauthenticated POST /ajax-api/3.0/mlflow/scorer/invoke, accept serialized third-party scorer data that Scorer.model_validate_json resolves using a module-path allowlist without constraining the selected class or its constructor arguments. When optional trulens and trulens-providers-litellm packages are installed, an attacker can select mlflow.genai.scorers.trulens, choose a model URI outside MLflow's native provider registry so execution uses the LiteLLM fallback, and supply api_base and api_key values that cause the server to send an outbound request to an attacker-chosen or internal host with attacker-controlled headers and body. The vulnerable deserialization occurs before a tracking-store lookup or job submission. This issue is fixed in version 3.17.0.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
mlflowby mlflow
>= 3.12.0rc0, < 3.17.0
Updated Nov 6, 2026View on NVD →
Detail

MLflow is an open-source AI engineering platform widely utilized by data scientists, developers, and researchers in the field of machine learning and artificial intelligence. It is primarily used for managing the machine learning lifecycle, including experimentation, reproducibility, and deployment. Its utility in automating machine learning workflows has made it indispensable in various industry and academic settings. MLflow provides integration options with numerous tools and services, thereby facilitating a seamless AI model development process. Organizations relying on MLflow benefit from streamlined collaboration and enhanced productivity across teams. Despite its widespread usage, the security of this platform is paramount given its integration into sensitive data environments.

This scanner specifically targets the Server-Side Request Forgery (SSRF) vulnerability present in versions of MLflow prior to 3.17.0. SSRF vulnerabilities can be exploited by attackers to coerce a server into making unauthorized requests to internal or external domains. Such vulnerabilities often result from improper validation of user input that is used in crafting network requests. An attacker can manipulate this flaw to access restricted resources, potentially leading to sensitive data exposure or unauthorized actions. Through this scanner, users can detect the presence of this vulnerability and take necessary actions to protect their systems.

The vulnerability allows unauthorized third-party data deserialization and execution through invocation endpoints within MLflow. During the exploitation process, attackers utilize the `/ajax-api/3.0/mlflow/scorer/invoke` endpoint with maliciously crafted payloads. These payloads influence the MLflow server to interact with attacker-specified domains, potentially leaking internal service data. The exploitation relies on certain packaged modules being available, which further enables the injection of external requests using arbitrary headers and body content. This creates opportunities for attackers to probe internal networks indirectly and escalate their attack vectors depending on the exposed systems.

Exploitation of this SSRF vulnerability can have severe repercussions including unauthorized access to internal services and metadata endpoints within a cloud environment. Potential impacts also involve exposure of sensitive information and the ability for attackers to perform further pivoting within a network. The exploitation could allow attackers to map internal infrastructure, collect intelligence or even execute subsequent attacks using discovered endpoints. Such breaches may lead to data exfiltration, loss of system integrity, and unauthorized manipulation of network-accessible resources if unaddressed.

REFERENCES

Solution Advice
  • Upgrade MLflow to version 3.17.0 or later to address the SSRF vulnerability by constraining third-party scorer classes and their constructor arguments.
  • Implement network-level access controls to restrict outbound requests from MLflow servers to trusted hosts only.
  • Review and audit the use of third-party packages in your MLflow environment and remove any unnecessary components that could introduce vulnerabilities.
  • Continuously monitor network traffic from MLflow deployments for unusual patterns that might indicate exploitation attempts.
  • Ensure that input validation is robust to prevent the injection of malicious parameters into server requests.

Get AI-powered remediation steps tailored to your asset.

Try AI Solutions →

Check your infrastructure.
Right now.

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