CVE-2026-64849
MLflow Server-Side Request Forgery Vulnerability
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.
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines. Deadline for federal agencies: 2026-09-02.
5 articles across 5 outlets · first covered Aug 18, 2026 · latest Aug 20, 2026
Coverage timeline
-
MLflow SSRF flaw leaks secrets, CISA urges immediate patchwww.securityweek.com · Aug 20, 2026
-
SSRF bug in MLflow (CVE-2026-64849) exposes cloud secretssecurityaffairs.com · Aug 20, 2026
-
CISA flags MLflow SSRF flaw CVE-2026-64849 in KEV catalogwww.cisa.gov · Aug 19, 2026
-
CISA Adds CVE-2026-64849 to Known Exploited Vulnerabilities Cataloguecisa.gov · Aug 19, 2026
-
MLflow SSRF flaw CVE-2026-64849 exposes internal servicessecurityonline.info · Aug 18, 2026