cve.bz

CVE-2026-64849 MLflow Server-Side Request Forgery Vulnerability

9.3 criticalKEVExploit referenceEPSS 10%Fix available

Critical (9.3) in MLflow MLflow. In CISA KEV since 2026-08-19. EPSS 10% estimated probability of exploitation activity in the next 30 days. Fixed in mlflow 3.15.0.

On this page
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.

Severity

CVSS 3.1

9.3 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
EPSS
10% (unchanged from 10% a week ago; 9.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 96th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-08-19, due 2026-09-02
CISA's assessment (SSVC)
Exploitation: active · Automatable: yes · Technical impact: partial, assessed 2026-08-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-64849 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-64849?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-64849?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-64849 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
lfprojects:mlflowfrom 3.3.0 before 3.15.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-7gwp-5pfp-969jPyPImlflow>=3.3.0 <3.15.03.15.0
PYSEC-2026-3687PyPImlflow<3.15.03.15.0

Red Hat

Red Hat rates this Important.

Red Hat's statement

This flaw is in MLflow Tracking Server webhook delivery. An attacker who can reach the MLflow API can abuse POST /api/2.0/mlflow/webhooks/{id}/test to trigger SSRF and read upstream response bodies. Upstream rates this against the default unauthenticated mlflow server (PR:N).

For OpenShift AI, the operator-managed odh-mlflow-rhel9 image is the primary exposure; the operator enables kubernetes-auth by default, so unauthenticated abuse applies only where MLflow is deployed without authentication. The other 19 RHOAI images embed the mlflow Python package as a client library and do not execute the vulnerable server webhook path in their default role concluding those 19 RHOAI images as Not Affected.

Impact is set to Important with PR:L reflecting typical authenticated RHOAI deployments.

Red Hat's mitigation

To reduce the attack surface for this vulnerability, restrict network access to the MLflow server. Implement firewall rules or network access controls to limit connectivity to the MLflow instance from untrusted networks. This operational control helps prevent unauthenticated attackers from reaching the vulnerable webhook test endpoint.

ProductPackageStateAdvisory
Red Hat OpenShift AI 3.4rhoai/odh-mlflow-rhel9:1787226790Fixed 2026-08-27RHSA-2026:60520
Red Hat OpenShift AI 3.5rhoai/odh-latency-predictor-prediction-rhel9:1786552271Fixed 2026-08-26RHSA-2026:60367
Red Hat OpenShift AI 3.5rhoai/odh-latency-predictor-training-rhel9:1786552250Fixed 2026-08-26RHSA-2026:60367
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-pytorch-rocm-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-tensorflow-cuda-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-pipeline-runtime-tensorflow-rocm-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-cpu-torch210-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-cuda130-torch210-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-th06-rocm64-torch291-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-training-cuda128-torch29-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9Not affected
Red Hat OpenShift AI (RHOAI)rhoai/odh-workbench-jupyter-tensorflow-rocm-py312-rhel9Not affected
1 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-64849.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON