MLflow AI Gateway permits SSRF through an unvalidated api_base

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

EPSS

• CVE-2026-71211: 0.29% estimated exploitation activity in the next 30 days; percentile 21.63 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

MLflow's AI Gateway accepts an authconfig.apibase value when creating a gateway secret (mlflow/server/handlers.py, creategatewaysecret) with no validation of scheme, host, or IP range; the value is stored verbatim. The gateway proxy endpoint (mlflow/server/gatewayapi.py, rawproxy) subsequently issues an HTTP request to that stored apibase plus a caller-supplied path and returns the full response body. MLflow's existing SSRF guard, validatewebhookurl (which blocks non-global and metadata IPs), is never invoked anywhere in this gateway secret/proxy code path. The CreateGatewaySecret action additionally has no entry in the permission-validator map, so it requires only basic authentication rather than any specific scope, meaning any authenticated user — including read-only accounts — can create a secret pointing at an internal address and reach it via the proxy endpoint, potentially exposing cloud-instance IAM credentials via metadata services. This is related to CVE-2026-4035, which…

Published by the source

5 Aug 2026, 09:31 UTC

Last modified by the source

31 Aug 2026, 19:48 UTC

Source last checked

26 Oct 2026, 13:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h7x2-h6g9-p789

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-71211

Advisory: MLflow AI Gateway permits SSRF through an unvalidated api_base
IDs: CVE-2026-71211, GHSA-h7x2-h6g9-p789
Record: https://patchnext.com/advisories/cve-2026-71211 (revision 1, source checked 26 Oct 2026, 13:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI mlflow: affected >= 3.13.0, <= 3.15.2

## Suggested inspection (read-only)
- `python -m pip show mlflow`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mlflow.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-h7x2-h6g9-p789 (GitHub-reviewed advisory GHSA-h7x2-h6g9-p789 lists affected ranges: PyPI mlflow >=3.13.0 <=3.15.2)

Commands are suggestions: review each one before running it.