S4E just found a high top 10 tcp port service scan
critical·Product Based Web Vulnerabilities·Updated Aug 18, 2026

CVE-2026-64849 Scanner

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

Est. Time~1 minutes
Scan TypeGroup Scan
Targetsdomain, subdomain, ipv4
CostFree
0
Times Used
by S4E users
0
Assets Scanned
domains & IPs
0
Vulnerabilities Found
confirmed findings
References
CVECVE-2026-64849
9.3
CVSScritical
Exploitable remotely over the internet · no authentication required.

MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. Prior to 3.15.0, the unauthenticated POST /api/2.0/mlflow/webhooks/{id}/test endpoint calls _validate_webhook_url() in mlflow/utils/validation.py only for the original URL while mlflow/webhooks/delivery.py follows redirects and re-resolves the hostname without pinning the validated address, allowing attackers to reach internal or cloud metadata services and receive response_status and response_body. This issue is fixed in version 3.15.0.

Attack Vector
Network
Privileges Req.
None
User Interaction
None
Affected
mlflowby mlflow
< 3.15.0
Updated Aug 18, 2026View on NVD →
Detail

MLflow is an open-source platform used by data scientists and developers for managing the machine learning lifecycle. It is designed to track experiments, manage machine learning models, and streamline the ML pipeline in order to improve efficiency and collaboration. MLflow is often deployed within enterprise environments to manage extensive data workflows and deployments seamlessly. Organizations leverage MLflow's capabilities for scalable experimentation and reproducible research. Integration with various cloud platforms and on-premise infrastructures allows diverse applications in different sectors. Because MLflow handles sensitive data and models, maintaining its security posture is paramount.

In the MLflow platform, a Server-Side Request Forgery (SSRF) vulnerability was identified which can be exploited by unauthorized individuals. This specific security flaw allows attackers to misuse webhooks for reaching and probing internal or cloud metadata services. The vulnerability stems from improper validation of webhook URLs, which can be manipulated to bypass intended access controls. Given the critical nature of this oversight, it poses a high risk of information disclosure. Attackers may exploit this to leak sensitive data or craft further attacks against the affected infrastructure.

This vulnerability resides in the post-authentication webhook management where the attackers manipulate the URL parameters. The use of unchecked redirection targets leads to improperly handling URL endpoints and DNS rebinding requests. The test endpoint for webhook URLs does not adequately safeguard against these misuse patterns, opening a path for attacks. During exploitation, messages are forcibly redirected to internal resources, bypassing the firewall restrictions present. The flaw exists specifically in MLflow versions above 3.15.0 and is marked by external influences tricking internal system calls via crafted webhook entries.

If exploited, this SSRF vulnerability may result in the exposure of confidential environment variables and internal cloud resources. Unauthorized users might access metadata services that can reveal sensitive configurations or secret keys. Furthermore, exploiting these flows can serve as a vector to network reconnaissance efforts, potentially leading to more severe compromises. Services that rely on these internal communications become vulnerable to data interception and unauthorized data manipulations. In worst-case scenarios, further exploitation might allow attackers to escalate privileges or deploy additional malicious payloads.

REFERENCES

Solution Advice
  • Upgrade MLflow to the latest version that includes PR #24258 which addresses the SSRF vulnerability.
  • Implement stringent input validation on webhook URLs to ensure authenticity and preclude misuse.
  • Utilize SSRF protection mechanisms to secure network communications in the application workflow.
  • Audit access permissions and restrict based on the principle of least privilege to reduce exposure risk.
  • Regularly monitor and log all webhook activities to quickly detect and respond to abnormal behaviors.

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.