CVE-2025-52967: SSRF
Published Jun 23, 2025
·Updated
gatewayproxyhandler in MLflow before 3.1.0 lacks gatewaypath validation.
Affected Software
2 affected componentsFixes available
MLflow MLflow<3.1.0
pip/mlflow<3.1.0
3.1.0
Event History
Jun 23, 2025
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·03:31 PM
Data Sourced
via GitHub·03:31 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2025-52967?
CVE-2025-52967 is considered a medium severity vulnerability due to the potential for unauthorized data access.
2
How do I fix CVE-2025-52967?
To fix CVE-2025-52967, upgrade MLflow to version 3.1.0 or later, which includes the necessary gateway_path validation.
3
What are the potential risks associated with CVE-2025-52967?
The risks associated with CVE-2025-52967 include potential data leaks and unauthorized access to the MLflow gateway.
4
What versions of MLflow are affected by CVE-2025-52967?
CVE-2025-52967 affects all versions of MLflow prior to 3.1.0.
5
Is there a workaround for CVE-2025-52967 if I cannot upgrade?
There is no official workaround for CVE-2025-52967, so upgrading to a secure version is strongly recommended.