Skip to content
Activamente explotadaCVSS 9.3 · CRITICAL

CVE-2026-64849SSRF sin autenticación en MLflow

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.

Ver en NVD

Análisis

MLflow is vulnerable to an unauthenticated Server-Side Request Forgery (SSRF) via its webhook testing endpoint. Attackers can exploit this to reach internal services or cloud metadata endpoints (IMDS) and view response bodies, potentially leading to credential theft.

Roles relevantes

PythonIADataScienceMachineLearningCloudBackend

Severidad

Puntaje: 9.3(CRITICAL)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
AV: NETWORK
AC: LOW
PR: NONE
UI: NONE
S: CHANGED
C: HIGH
I: LOW
A: NONE
Tipo de falla (CWE): CWE-918

CISA KEV

Agregada al KEV: 2026-08-19
Fecha límite federal: 2026-09-02
Uso conocido en ransomware: Unknown
Acción requerida

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.

EPSS

Probabilidad de explotación (próx. 30 días): 0.0111 (1.1%)
Percentil: 63.3%
EPSS: 2026-08-19

Afecta

lfprojects:mlflow

Descripción técnica

MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. 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.

Publicada: 17/8/2026, 22:17:23
Última modificación: 19/8/2026, 19:23:24

Referencias

InicioEventosBlogRecursosCursosEquipo