CVE-2026-71211 mlflow - Unvalidated Gateway Secret api_base Enables SSRF via Gateway Proxy Endpoint

High 7.1 Published Updated

Attackers can exploit unvalidated API base URLs in MLflow's AI Gateway to perform Server-Side Request Forgery, accessing internal resources via the proxy endpoint.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-71211?

CVE-2026-71211 is a high-severity server-side request forgery vulnerability in mlflow, published on 5 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

MLflow's AI Gateway accepts an auth_config.api_base value when creating a gateway secret (mlflow/server/handlers.py, _create_gateway_secret) with no validation of scheme, host, or IP range; the value is stored verbatim. The gateway proxy endpoint (mlflow/server/gateway_api.py, raw_proxy) subsequently issues an HTTP request to that stored api_base plus a caller-supplied path and returns the full response body.

Weakness: CWE-918

Which versions are affected by CVE-2026-71211?

3 open source packages ship an affected version, including mlflow.

PackageAffectedFixed in
mlflow PyPIFrom 3.13.0 to 3.15.2None
mlflow PyPIFrom 3.13.0 to 3.15.2None
mlflow PyPIFrom 3.13.0 to 3.15.2None

How do I fix CVE-2026-71211?

Apply the vendor's patch.

Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.

Is CVE-2026-71211 being exploited?

There is no known exploitation of CVE-2026-71211 in the wild and no public exploit code.

Public exploit code: 1 proofs of concept on GitHub.

Sources

Also known as GHSA-h7x2-h6g9-p789, MINI-wr6r-7322-h4q6, PYSEC-2026-3865.

Is CVE-2026-71211 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free