CVE-2026-64849

{"id": "CVE-2026-64849", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-64849", "role": "CISA Coordinator", "options": [{"exploitation": "active"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-08-20T03:55:29.820245Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security-advisories@github.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 9.3, "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 4.7, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security-advisories@github.com", "affectedData": [{"vendor": "mlflow", "product": "mlflow", "versions": [{"status": "affected", "version": ">= 3.3.0, < 3.15.0"}]}]}], "published": "2026-08-17T22:17:23.580", "references": [{"url": "https://github.com/mlflow/mlflow/commit/ba949522477cbd5915aa55d29b0cfad7d5ddf939", "tags": ["Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/mlflow/mlflow/issues/24179", "tags": ["Exploit", "Issue Tracking", "Mitigation"], "source": "security-advisories@github.com"}, {"url": "https://github.com/mlflow/mlflow/pull/24258", "tags": ["Issue Tracking", "Patch"], "source": "security-advisories@github.com"}, {"url": "https://github.com/mlflow/mlflow/releases/tag/v3.15.0", "tags": ["Release Notes"], "source": "security-advisories@github.com"}, {"url": "https://github.com/mlflow/mlflow/security/advisories/GHSA-7gwp-5pfp-969j", "tags": ["Exploit", "Vendor Advisory"], "source": "security-advisories@github.com"}, {"url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-64849", "tags": ["US Government Resource"], "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "security-advisories@github.com", "description": [{"lang": "en", "value": "CWE-918"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "MLflow es una plataforma de ingenier\u00eda de IA de c\u00f3digo abierto para agentes, modelos de lenguaje grandes y modelos de aprendizaje autom\u00e1tico. A partir de la versi\u00f3n 3.3.0 y versiones anteriores a la 3.15.0, el endpoint POST /api/2.0/mlflow/webhooks/{id}/test no autenticado llama a _validate_webhook_url() en mlflow/utils/validation.py solo para la URL original, mientras que mlflow/webhooks/delivery.py sigue las redirecciones y resuelve de nuevo el nombre de host sin fijar la direcci\u00f3n validada, lo que permite a los atacantes alcanzar servicios de metadatos internos o en la nube y recibir response_status y response_body. Este problema se ha solucionado en la versi\u00f3n 3.15.0."}], "lastModified": "2026-10-26T13:10:00.140", "cisaActionDue": "2026-09-02", "cisaExploitAdd": "2026-08-19", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:lfprojects:mlflow:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "1020A84A-9C92-4581-ADC4-4522AD465BA2", "versionEndExcluding": "3.15.0", "versionStartIncluding": "3.3.0"}], "operator": "OR"}]}], "sourceIdentifier": "security-advisories@github.com", "cisaRequiredAction": "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA\u2019s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA\u2019s \u201cForensics Triage Requirements\u201d (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.", "cisaVulnerabilityName": "MLflow Server-Side Request Forgery Vulnerability"}