CVE-2026-64849
CriticalExploitedPublic exploitMLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebinding)
Published Aug 17, 2026 · Updated Oct 7, 2026 · Also known as BIT-mlflow-2026-64849, EUVD-2026-60473, GHSA-7gwp-5pfp-969j, PYSEC-2026-3687
Key Facts
Patch immediately- CVE-2026-64849 is a critical-severity vulnerability (CVSS 9.3 v3.1) affecting MLflow (Lfprojects), rhoai/odh-mlflow-rhel9:1787226790 (redhat).
- It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Aug 18, 2026. Public exploit code is available.
- EPSS estimates a 9.8% probability of exploitation in the next 30 days.
- Fixed versions are available, including MLflow 3.15.0, MLflow 3.15.0-r0, MLflow 3.16.0-r0.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
CVSS v3.1
9.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
EPSS (30-day exploit likelihood)
9.8%
Higher than 95.5% of all scored CVEs
Exploited in the wild
Yes
4 catalog listings
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2026-64849 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
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.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| CISA KEV | Aug 19, 2026 | Sep 2, 2026 | Not reported |
| Industry KEV feed | Aug 18, 2026 | Sep 2, 2026 | Not reported |
| CIRCL KEV | Aug 18, 2026 | Sep 2, 2026 | Not reported |
| ENISA EUVD | Aug 19, 2026 | n/a | Not reported |
Required action: 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.
Affected Products
8 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| MLflowLfprojects | See advisory | 3.15.0 |
| rhoai/odh-mlflow-rhel9:1787226790redhat | See advisory | n/a |
Patched Releases
MLflow
3.15.0, 3.15.0-r0, 3.16.0-r0
Timeline
Publicly disclosed
Aug 17, 2026
Added to Industry KEV feed
Aug 18, 2026
Added to CIRCL KEV
Aug 18, 2026
Added to CISA KEV
Aug 19, 2026
Added to ENISA EUVD
Aug 19, 2026
Last updated
Oct 7, 2026
Weakness Type
- CWE-918 Server-Side Request Forgery (SSRF)
References
- advisoryRHSA-2026:60520
- advisoryGHSA advisory
- advisoryhttps://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64849.json
- advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2026-64849
- exploitVulnCheck exploitation report
FAQ
Common Questions.
MLflow is an open source AI engineering platform for agents, large language models, and machine learning models.
Affected: MLflow (Lfprojects); rhoai/odh-mlflow-rhel9:1787226790 (redhat). The full list is in the CVE brief.
It is exploited in the wild, listed in CISA KEV, Industry KEV feed, CIRCL KEV, ENISA EUVD since Aug 18, 2026.
Yes. It was added on Aug 19, 2026 with a federal remediation due date of Sep 2, 2026.
Public exploit code is available.
Fixed versions are available, including MLflow 3.15.0, MLflow 3.15.0-r0, MLflow 3.16.0-r0.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2026-64849 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo