MLflow Server-Side Request Forgery Vulnerability
CVE-2026-64849 Exploited
MLflow contains a server-side request forgery vulnerability that can allow attackers to reach internal or cloud metadata services and receive responsestatus and responsebody.
Being exploited in the wild
Catalogued 19 August 2026 · US federal remediation deadline 2 September 2026
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…
Exploit code is also public: Public PoC · Nuclei template
- NucleiMLflow Webhook SSRF - Unauthenticated Full-Read via Redirect Bypass
- Public PoCcodeb0ssx/CVE-2026-64849-PoC
- Public PoCBiuTrap/CVE-2026-64849
- Public PoCzavisco/CVE-2026-64849.yaml
- Public PoCisaca0315/CVE-2026-64849-poc-lab
- Public PoCmaxprog-svg/CVE-2026-64849
Part of the AI stack
This affects MLflow, in Training & MLOps.
Assessment
- CVSS
- Not yet scored
- Severity
- Unscored
- Known exploited
- Yes — listed in the CISA KEV catalog
- Exploit availability
- CISA KEV, Public PoC, Nuclei template
- Published
- 19 August 2026
- Last updated
- 19 August 2026
- Affected
- MLflow · MLflow
- Weakness
- CWE-918
At the source
References
Query this programmatically
Agents can read this through the MCP endpoint, or over HTTP:
curl https://cve.zerocrew.in/api/cve/CVE-2026-64849