A critical security vulnerability in MLFlow allows unauthenticated attackers to bypass Same-Origin Policy protections through DNS rebinding, enabling unauthorized manipulation or exfiltration of experiment data.

The vulnerability is caused by a failure to validate the Origin header in the MLFlow REST server, which exposes the system to DNS rebinding attacks. This flaw allows an unauthenticated attacker to execute unauthorized REST API calls, including querying, updating, or deleting sensitive experiment data.

The exploitation of this vulnerability could lead to the complete compromise of machine learning experiment data, including the destruction or unauthorized modification of proprietary models and datasets. Given the CVSS score of 8.1, the risk of data exfiltration and integrity loss is significant, potentially resulting in severe operational disruption and loss of intellectual property.

Immediate Action: Update the MLFlow installation to version 3.5.0 or later to implement the required Origin header validation.

Proactive Monitoring: Review web server access logs for anomalous requests originating from unexpected domains or patterns indicative of DNS rebinding attempts.

Compensating Controls: Deploy a Web Application Firewall (WAF) or configure reverse proxy rules to strictly validate the Host and Origin headers of incoming requests until the patch can be applied.

Public Exploit Available: No (exploit_available: unknown)

The vulnerability represents a high risk to data integrity and confidentiality within MLFlow environments. Organizations should prioritize the update to version 3.5.0 immediately to remediate the underlying lack of origin validation. If patching is not immediately feasible, network-level controls to restrict access to the REST interface are strongly advised.