← gociux.comall exploited CVEs

Exploited vulnerability · CISA KEV

Is CVE-2026-64849 exploited? Yes: in CISA KEV since 19 Aug 2026

Gociux · MLflow · data: CISA KEV, CVE record, FIRST EPSS

Yes. CVE-2026-64849, MLflow Server-Side Request Forgery Vulnerability, is being exploited in the wild. CISA added it to its Known Exploited Vulnerabilities catalog on 19 Aug 2026, 2 days after it was published. It affects MLflow. If you run it, CISA's required action is: 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.

exploitedYesCISA KEV · 19 Aug 2026
ransomwareNot knownno confirmed use
EPSStop 5%very likely to be exploited
severity9.3CVSS 3.1 · critical
US federal due2 Sep 2026BOD 22-01 deadline

What it is

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.

VendorMLflow (1 exploited CVE in KEV)
ProductMLflow
VulnerabilityMLflow Server-Side Request Forgery Vulnerability
WeaknessCWE-918
Published17 Aug 2026
Added to KEV19 Aug 2026
Reported by (CNA)GitHub_M

What to do

  1. Check whether you run it. Look for MLflow in your asset inventory, including appliances and cloud images. Stack check lists every exploited MLflow CVE at once.
  2. Apply the fix. 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.
  3. If you can't patch today, take the affected service off the internet or restrict who can reach it, and check its logs for signs of compromise since 17 Aug 2026.
  4. Get told next time. Email alerts when CISA adds a CVE for MLflow.

References

Questions

Is CVE-2026-64849 being exploited?

Yes. CISA added CVE-2026-64849 to the Known Exploited Vulnerabilities catalog on 19 Aug 2026, which means there is reliable evidence of exploitation in the wild.

Is CVE-2026-64849 used in ransomware attacks?

CISA does not list known ransomware use for it. That can change, and exploitation alone is reason to fix it first.

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 (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. Check MLflow's advisory for the fixed versions, and if you can't patch quickly, restrict access to the affected MLflow and watch it for signs of compromise.

Sources: CISA KEV (exploitation, ransomware use, required action, due date), the CVE record (publication date, CVSS, CNA), NVD and FIRST EPSS (live score). More: all KEV additions in August 2026 · act-now radar.

Running MLflow in a regulated environment?

We check exposure across your estate, patch or mitigate with your team, and set up detection for what attackers do after exploiting it.

Get in touch →