Critical 9.3Known exploited (CISA KEV)Published Aug 17, 2026

CVE-2026-64849MLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebinding)

Updated under an hour ago (Oct 27, 2026, 4:30 AM ET)

Does this affect you?

It affects mlflow and 1 other product. Add what you run to find out whether that includes you.

CISA lists it as known exploited since Aug 19, 2026; federal agencies had to remediate by Sep 2, 2026. Treat that date as your deadline.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for mlflow

Exploited in the last 30 days

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.

CVSS: 9.3 CRITICAL (v3.1, CNA)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
Weakness (CWE): CWE-918
Known exploited: Added to CISA KEV Aug 19, 2026; federal remediation due Sep 2, 2026Apply 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.
EPSS (exploitation in the next 30 days): 10.02% (percentile 96)
Assigned by: GitHub_M
NVD analysis: Analyzed
Record last updated: Oct 2, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

mlflow mlflow mlflow:mlflow (from the name)	from 3.3.0, < 3.15.0	CNA record
lfprojects mlflow lfprojects:mlflow	from 3.3.0 before 3.15.0	NVD

References

References

https://github.com/mlflow/mlflow/security/advisories/GHSA-7gwp-5pfp-969j	x-refsource-confirm, exploit, vendor-advisory
https://github.com/mlflow/mlflow/issues/24179	x-refsource-misc, exploit, issue-tracking, mitigation
https://github.com/mlflow/mlflow/pull/24258	x-refsource-misc, issue-tracking, patch
https://github.com/mlflow/mlflow/commit/ba949522477cbd5915aa55d29b0cfad7d5ddf939	x-refsource-misc, patch
https://github.com/mlflow/mlflow/releases/tag/v3.15.0	x-refsource-misc, release-notes
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-64849	us-government-resource

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.