CVE-2026-64849
MLflow contains a server-side request forgery vulnerability that can allow attackers to reach internal or cloud metadata services and receive response_status and response_body.
MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. Starting in 3.3.0 and 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N- github.com/mlflow/mlflow/commit/ba949522477cbd5915aa55d29b0cfad7d5ddf939Patch
- github.com/mlflow/mlflow/issues/24179ExploitIssue Tracking
- github.com/mlflow/mlflow/pull/24258Issue TrackingPatch
- github.com/mlflow/mlflow/releases/tag/v3.15.0Release Notes
- github.com/mlflow/mlflow/security/advisories/GHSA-7gwp-5pfp-969jExploitVendor Advisory
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-64849US Government Resource
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 54 days
- CVSS
- 9.3 CRITICAL
- EPSS (30-day exploit probability)
- 10.0% · top 4% of all CVEs
- Weakness
- CWE-918
- Attack vector
- Network, remotely reachable
- Preconditions
- No privileges and no user interaction
- 1.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.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.