Quick answer
Yes. CVE-2026-64849 in MLflow MLflow is being exploited by attackers: CISA added it to its Known Exploited Vulnerabilities catalogue on August 19, 2026. If you run MLflow, apply the vendor's fix now and check for signs of compromise.
What is CVE-2026-64849?
MLflow Server-Side Request Forgery Vulnerability. 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.
Description from the CISA Known Exploited Vulnerabilities catalogue.
What kind of flaw is it?
The server can be made to send requests on the attacker's behalf, often reaching internal systems or cloud credentials.
Other exploited server-side request forgery (ssrf) How it worksWhy it matters
AI tooling such as model servers, workflow builders and agent frameworks is being deployed quickly, often without the hardening applied to other software. Exploited flaws can expose models, data, API keys and the systems AI agents are connected to.
Higher than 96% of all scored vulnerabilities.
Am I affected? How to check | What to do now |
|---|---|
1Inventory AI tools in use, including those deployed by data science or innovation teams. | 1Apply the fix and remove internet exposure. |
2Check versions and whether the tool is reachable from the internet. | 2Rotate API keys and credentials held by the tool. |
3Review stored API keys and connected data sources for exposure. | 3Bring AI tooling into normal vulnerability management and testing. |
Am I affected? How to check
- 1Inventory AI tools in use, including those deployed by data science or innovation teams.
- 2Check versions and whether the tool is reachable from the internet.
- 3Review stored API keys and connected data sources for exposure.
What to do now
- 1Apply the fix and remove internet exposure.
- 2Rotate API keys and credentials held by the tool.
- 3Bring AI tooling into normal vulnerability management and testing.
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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 and priority
CISA requires US federal civilian agencies to remediate catalogued vulnerabilities by the listed due date under Binding Operational Directive 22-01 (September 2, 2026 for this one), and strongly urges every organization to prioritize them the same way.
Common questions
Is CVE-2026-64849 being exploited?
Yes. It is listed in CISA's Known Exploited Vulnerabilities catalogue, which only includes vulnerabilities with confirmed exploitation in the wild. It was added on August 19, 2026.
How do I fix CVE-2026-64849?
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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. Check the vendor advisory for fixed versions, and if the system was exposed while unpatched, investigate it for signs of compromise.
Is my MLflow MLflow affected?
Check your installed version against the vendor advisory linked on this page. If the affected component is reachable from the internet and unpatched, assume it is at risk and act immediately.