MLflow Server-Side Request Forgery Vulnerability

MLflow 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. Added to CISA KEV on 2026-08-19 (federal deadline 2026-09-02).

First seen: 19 Aug 2026
Last update: 19 Aug 2026, 12:00 UTC
Identifiers: CVE-2026-64849
Source: CISA KEV
On the menu as: ML infra

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## MLflow Server-Side Request Forgery Vulnerability
Severity: high, exploited in the wild. Patch status: patched.
Affected: MLflow MLflow
Ids: CVE-2026-64849

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. Added to CISA KEV on 2026-08-19 (federal deadline 2026-09-02).

## Steps
1. Search the repo, its CI and infra config for MLflow MLflow. If present, report the version in use and whether it's affected.

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve("CVE-2026-64849") for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://github.com/mlflow/mlflow/issues/24179 https://github.com/mlflow/mlflow/pull/24258 https://nvd.nist.gov/vuln/detail/CVE-2026-64849
https://pwned.coffee/i/mlflow-server-side-request-forgery-vulnerability-cve-2026-64849

Sources

Totalone hot coffee