CVE-2026-64849
MLflow Server-Side Request Forgery
- Published17 Aug 2026
- Added to CISA KEV19 Aug 2026
- Remediation due2 Sept 2026
Description
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 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:NAffected products
Remediation
References
- https://github.com/mlflow/mlflow/commit/ba949522477cbd5915aa55d29b0cfad7d5ddf939
- https://github.com/mlflow/mlflow/issues/24179
- https://github.com/mlflow/mlflow/pull/24258
- https://github.com/mlflow/mlflow/releases/tag/v3.15.0
- https://github.com/mlflow/mlflow/security/advisories/GHSA-7gwp-5pfp-969j
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-64849
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-64849 being actively exploited?
Yes. CVE-2026-64849 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 19 Aug 2026.
How severe is CVE-2026-64849?
CVE-2026-64849 has a CVSS 3.1 base score of 9.3, rated critical. EPSS estimates a 9.84% probability of exploitation.
Which products are affected by CVE-2026-64849?
Affected products include Lfprojects Mlflow.
How do I fix CVE-2026-64849?
Upgrade affected software to a fixed version, for example Lfprojects Mlflow 3.15.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-64849 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.