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

> 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.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Aug 2026
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-h7x2-h6g9-p789, MINI-wr6r-7322-h4q6, PYSEC-2026-3865

## 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 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-71211?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mlflow` | PyPI | From 3.13.0 to 3.15.2 | None |
| `mlflow` | PyPI | From 3.13.0 to 3.15.2 | None |
| `mlflow` | PyPI | From 3.13.0 to 3.15.2 | None |

## How do I fix CVE-2026-71211?

Apply the vendor's patch.

## 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:

- CVE-2026-71211 exploit (github_poc): https://github.com/Abdivasiyev2008/CVE-2026-71211-exploit

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71211 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-71211 in the wild and no public exploit code.

Affected packages and fixed versions:
- mlflow (PyPI): affected from 3.13.0 up to 3.15.2; no fix listed
- mlflow (PyPI): affected from 3.13.0 up to 3.15.2; no fix listed
- mlflow (PyPI): affected from 3.13.0 up to 3.15.2; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-71211/ (Markdown: https://insights.sbomify.com/CVE-2026-71211/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71211
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71211
- OSV: https://osv.dev/vulnerability/CVE-2026-71211

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-71211/
Summaries are generated and may contain mistakes; the official description above is the record.