CVE-2026-64849

MLflow server-side request forgery, confirmed exploited in the wild.

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.

Check your domain free How we watch for this

10%chance of exploitation in the next 30 days (EPSS), 95th percentile

19 Augadded to CISA's Known Exploited Vulnerabilities list, 2026

2 Sepfederal remediation deadline, already passed

Passedpast the deadline: patch now

CISA's name for it	MLflow Server-Side Request Forgery Vulnerability
Vendor and product	MLflow · MLflow
Type	server-side request forgery · CWE-918
Exploited	Confirmed by CISA listed 19 August 2026
Likelihood	one of the most likely to be exploited of every vulnerability tracked
Deadline	2 September 2026 · already passed
Used in ransomware	Not reported
Advisories	github.com ↗ · github.com ↗ · www.cisa.gov ↗ · www.cisa.gov ↗

What to do

Three steps, in this order

Step 1

Apply the vendor's fix or mitigation; CISA lists only vulnerabilities seen exploited.

Step 2

If you cannot patch now, restrict network access to the affected product.

Step 3

Check for signs of compromise since the date it was added to the list.

CISA's 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.

CISA's 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.

Is it on your estate?

Know before someone else finds it

Threat Landscape Monitoring fingerprints the software your internet-facing hosts disclose and matches it, every day, against this list and the exploitation scores. When a new entry touches something you run, you are told once, with the host and the fix. The free plan covers one domain.

Start free with one domain Run the free domain check

Questions

CVE-2026-64849 in short

Is CVE-2026-64849 being exploited?

Yes. CISA added CVE-2026-64849 to its Known Exploited Vulnerabilities catalogue on 19 August 2026, which it does only on evidence of exploitation in the wild.

What is the CISA deadline for CVE-2026-64849?

US federal agencies must remediate it by 2 September 2026. Everyone else should treat that date as the latest safe point to patch an internet-facing system.

How likely is CVE-2026-64849 to be exploited in the next 30 days?

FIRST's Exploit Prediction Scoring System gives it 10%, the 95th percentile of every CVE it scores.

How do I fix CVE-2026-64849?

Apply the vendor's fix or mitigation; CISA lists only vulnerabilities seen exploited. If you cannot patch now, restrict network access to the affected product. Check for signs of compromise since the date it was added to the list.

Sources: CISA Known Exploited Vulnerabilities catalogue (released 10 November 2026) and FIRST EPSS. Page compiled automatically by SAK T.L.M, the threat-intelligence tool of SAK T.E.C, on 13 November 2026.