← Übersicht Nicht im beobachteten Stack

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

CVE-2026-64849 · BIT-mlflow-2026-64849 · GHSA-7gwp-5pfp-969j · PYSEC-2026-3687 · WID-SEC-W-2026-2946

Aktiv ausgenutzt (CISA KEV) Kritisch · CVSS 9.3 BSI: hochRed Hat: Important Netzwerk · ohne Login Kein Fix bekannt

Aktive Ausnutzung bestätigt.

CISA führt diese Schwachstelle seit 19.08.2026 im Katalog der ausgenutzten Schwachstellen. Frist für US-Bundesbehörden: 02.09.2026.

Vorgabe von CISA: 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.

Veröffentlicht
17.08.2026 23:16
Zuletzt geändert
19.11.2026
EPSS (30 Tage)
10.0 %
CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

Beschreibung

Originaltext der Quelle, nicht übersetzt.

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 POST /api/2.0/mlflow/webhooks/{id}/test endpoint (accessible without credentials when server authentication is not enabled) 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. The unauthenticated attack scenario described here applies to deployments without authentication. With MLflow’s built-in basic authentication enabled, requests to this endpoint require valid credentials; this issue does not itself bypass authentication. This issue is fixed in version 3.15.0.

Status beim Hersteller

Red Hat stuft seine Produktlinien ein: 1 betroffen, 2 behoben, 2 nicht betroffen.

Open Source MLflow <=3.13.0 Betroffen
Red Hat OpenShift AI 3.4 Behoben rhoai/odh-mlflow-rhel9 RHSA-2026:60520
Red Hat OpenShift AI 3.5 Behoben rhoai/odh-latency-predictor-prediction-rhel9, rhoai/odh-latency-predictor-training-rhel9 RHSA-2026:60367
Nicht betroffen (2)
Red Hat OpenShift AI (RHOAI)Nicht betroffenverwundbarer Code nicht enthaltenrhoai/odh-pipeline-runtime-datascience-cpu-py312-rhel9, rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9, rhoai/odh-pipeline-runtime-pytorch-llmcompressor-cuda-py312-rhel9, rhoai/odh-pipeline-runtime-pytorch-rocm-py312-rhel9, rhoai/odh-pipeline-runtime-tensorflow-cuda-py312-rhel9, rhoai/odh-pipeline-runtime-tensorflow-rocm-py312-rhel9, rhoai/odh-th06-cpu-torch210-py312-rhel9, rhoai/odh-th06-cuda130-torch210-py312-rhel9, rhoai/odh-th06-rocm64-torch291-py312-rhel9, rhoai/odh-training-cuda128-torch29-py312-rhel9, rhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9, rhoai/odh-workbench-jupyter-datascience-cpu-py312-rhel9, rhoai/odh-workbench-jupyter-pytorch-cuda-py312-rhel9, rhoai/odh-workbench-jupyter-pytorch-llmcompressor-cuda-py312-rhel9, rhoai/odh-workbench-jupyter-pytorch-rocm-py312-rhel9, rhoai/odh-workbench-jupyter-tensorflow-cuda-py312-rhel9, rhoai/odh-workbench-jupyter-tensorflow-rocm-py312-rhel9, rhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9
Red Hat OpenShift AI 3.4Nicht betroffenverwundbarer Code nicht enthaltenrhoai/odh-ai-gateway-payload-processing-rhel9, rhoai/odh-automl-rhel9, rhoai/odh-autorag-rhel9, rhoai/odh-built-in-detector-rhel9, rhoai/odh-cli-rhel9, rhoai/odh-dashboard-rhel9, rhoai/odh-data-science-pipelines-argo-argoexec-rhel9, rhoai/odh-data-science-pipelines-argo-workflowcontroller-rhel9, rhoai/odh-data-science-pipelines-operator-controller-rhel9, rhoai/odh-eval-hub-rhel9, rhoai/odh-feast-operator-rhel9, rhoai/odh-feature-server-rhel9, rhoai/odh-fms-guardrails-orchestrator-rhel9, rhoai/odh-guardrails-detector-huggingface-runtime-rhel9, rhoai/odh-kf-notebook-controller-rhel9, rhoai/odh-kserve-agent-rhel9, rhoai/odh-kserve-autogluon-server-rhel9, rhoai/odh-kserve-controller-rhel9, rhoai/odh-kserve-llmisvc-controller-rhel9, rhoai/odh-kserve-router-rhel9, rhoai/odh-kserve-storage-initializer-rhel9, rhoai/odh-kube-auth-proxy-rhel9, rhoai/odh-kuberay-operator-controller-rhel9, rhoai/odh-llama-stack-core-rhel9, rhoai/odh-llama-stack-k8s-operator-rhel9 und 80 weitere
Weitere betroffene Pakete (5)
Bitnamimlflow3.3.0 → 3.15.0BIT-mlflow-2026-64849
CVEmlflow/mlflowkein Fix bekanntCVE-2026-64849
NVDlfprojects:mlflow3.3.0 → 3.15.0CVE-2026-64849
PyPImlflow3.3.0 → 3.15.0GHSA-7gwp-5pfp-969j
PyPImlflow3.15.0PYSEC-2026-3687

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.