MediumVulnerability
CVE-2025-52967: MLflow gateway_proxy_handler server-side request forgery via gateway_path
- Source
- NVD(opens in a new tab)
- Identifier
- CVE-2025-52967
- Published
- Record updated
- Affected
- mlflow >= 3.0.0rc0, < 3.1.0, fixed in 3.1.0, released June 10, 2025, 13 days before disclosure
- mlflow < 2.22.2, fixed in 2.22.2, released August 28, 2025, 66 days after disclosure
- Known exploitation
- Not listed in the CISA Known Exploited Vulnerabilities catalog at the last check.
- EPSS
- 0.4%
Summary
CVE-2025-52967 affects gateway_proxy_handler in MLflow versions before 3.1.0, which lacks validation of gateway_path. The flaw is classified as CWE-918, Server-Side Request Forgery (SSRF). NVD has not yet provided an assessment.
Mitigation
Fixed in 3.1.0 (see https://github.com/mlflow/mlflow/releases/tag/v3.1.0).
Affected packages in the Exposure Registry
Matched by package name and ecosystem. Each entry shows whether the package delegates to a language model and how many tracked packages depend on it.
- mlflowPyPILLM dependency since 2024-05-30 · 17 tracked dependents
Related items
- MediumCVE-2026-121936: easyVoice server-side request forgery through openaiBaseUrl in /api/v1/ttsSimilar attack · NVD/CVE Database
- MediumCVE-2026-118628: MLflow get-artifacts server-side request forgery information disclosureSimilar attack · NVD/CVE Database
- HighCVE-2026-118625: MLflow Tracking Server privilege escalation via get_endpointsSimilar attack · NVD/CVE Database
- InfoWhen trust becomes the payload: Inside the threats, etc quarterly reportSimilar attack · Elastic Security Labs
- MediumCritical Langflow flaws enable authentication bypass and RCESimilar attack · CSO Online