CVE-2026-64849
Act now ● On CISA KEV — actively exploited
Actively exploited — on the CISA KEV list.
CVSS base
9.3
CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
EPSS — probability of exploitation (30 days)
16.4%
96.8th percentile
CISA KEV
Listed
Added 2026-08-19 · patch by 2026-09-02
Weakness / dates
CWE-918
Published 2026-08-17 · modified 2026-08-20
CVSS breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
| Attack Vector | N | Network |
| Attack Complexity | L | Low |
| Privileges Required | N | None |
| User Interaction | N | None |
| Scope | C | Changed |
| Confidentiality | H | High |
| Integrity | L | Low |
| Availability | N | None |
Timeline
- 2026-08-17 — Published (NVD)
- 2026-08-19 — Added to CISA KEV (actively exploited)
- 2026-09-02 — CISA patch-by deadline
- 2026-08-20 — Last modified (NVD)
Description
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.
Affected
References
- https://github.com/mlflow/mlflow/commit/ba949522477cbd5915aa55d29b0cfad7d5ddf939
- exploit https://github.com/mlflow/mlflow/issues/24179
- https://github.com/mlflow/mlflow/pull/24258
- https://github.com/mlflow/mlflow/releases/tag/v3.15.0
- exploit https://github.com/mlflow/mlflow/security/advisories/GHSA-7gwp-5pfp-969j
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-64849