Descrizione
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.
Come correggere
Priorità: Urgente — intervenire subito, entro 24-48 ore. Motivazione: sfruttata attivamente (catalogo CISA KEV), CVSS 9.3.
Versioni da aggiornare
- Lfprojects Mlflow: vulnerabili le versioni dalla
3.3.0precedenti alla3.15.0→ aggiornare alla3.15.0o successiva.
Azione richiesta da CISA (KEV)
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.
Scadenza fissata per le agenzie federali USA: 2026-09-02. È un buon riferimento anche per le organizzazioni private.
Patch e advisory
- Patch: github.com/mlflow/mlflow/commit/ba949522477cbd5…
- Patch: github.com/mlflow/mlflow/pull/24258
- Note di rilascio: github.com/mlflow/mlflow/releases/tag/v3.15.0
Mitigazioni temporanee
Da applicare solo se non è possibile aggiornare subito:
- Applicare filtri sul traffico in uscita del server e bloccare l'accesso agli endpoint di metadati cloud (169.254.169.254).
Verifica
- Individuare tutti gli asset con il prodotto interessato (inventario, scanner di vulnerabilità, CMDB).
- Confrontare la versione installata con quelle indicate sopra.
- Applicare l'aggiornamento in un ambiente di test, poi in produzione; riavviare i servizi se richiesto.
- Ripetere la scansione per confermare la correzione.
- Poiché la vulnerabilità è sfruttata attivamente, cercare indicatori di compromissione nei log precedenti alla patch.
Configurazioni interessate
| Vendor | Prodotto | Versioni vulnerabili | Corretta in |
|---|---|---|---|
| Lfprojects | Mlflow | ≥ 3.3.0 < 3.15.0 | 3.15.0 |
Riferimenti
- Patchhttps://github.com/mlflow/mlflow/commit/ba949522477cbd5915aa55d29b0cfad7d5ddf939
- Patchhttps://github.com/mlflow/mlflow/pull/24258
- Exploit pubblicohttps://github.com/mlflow/mlflow/security/advisories/GHSA-7gwp-5pfp-969j
- Exploit pubblicohttps://github.com/mlflow/mlflow/issues/24179
- Note di rilasciohttps://github.com/mlflow/mlflow/releases/tag/v3.15.0
- Riferimentohttps://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-64849