NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

CVE-2025-52967 — mlflow

MEDIUMFix: mlflow/mlflow#15970

CVE-2025-52967 is a medium-severity (CVSS 5.8) Server-Side Request Forgery (SSRF) vulnerability in mlflow. A fix is available for mlflow — see the affected versions and patch details below.

MLFlow SSRF via gateway_proxy_handler

Also known asBIT-mlflow-2025-52967GHSA-wxj7-3fx5-pp9mPYSEC-2025-52
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-52967.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk-0.00%
Lower risk than most CVEs38th percentile — riskier than 38% of all scored CVEsHighest risk
0.00%0.31%0.63%0.94%0.2%0.4%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐍mlflow🐍mlflow

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

gateway_proxy_handler in MLflow before 3.1.0 lacks gateway_path validation.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPImlflow≥ 3.0.0rc0&&< 3.1.03.1.0pip install --upgrade 'mlflow==3.1.0'
🐍PyPImlflowall versions2.22.2pip install --upgrade 'mlflow==2.22.2'

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mlflow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update mlflow to 3.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-52967 is resolved across your whole dependency graph.

  3. Workarounds

    Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

gateway_proxy_handler in MLflow before 3.1.0 lacks gateway_path validation.
O3 Security · Impact-Aware SCA

Is CVE-2025-52967 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2025-52967: mlflow — Fixed in 3.1.0