# CVE-2025-14279: mlflow β€” Fixed in 3.5.0 🐍 🐍 PyPI Not in CISA KEV HIGH severity # CVE-2025-14279 β€” mlflow HIGH [Fix: mlflow/mlflow@b0ffd28](https://github.com/mlflow/mlflow/commit/b0ffd289e9b0d0cc32c9e3a9b9f3843ae83dbec3) CVE-2025-14279 is a high-severity (CVSS 8.1) CWE-346 vulnerability in mlflow. A fix is available for mlflow β€” see the affected versions and patch details below. DNS Rebinding Vulnerability in mlflow/mlflow Also known asBIT-mlflow-2025-14279[GHSA-pgqp-8h46-6x4j](/vulnerability/GHSA-pgqp-8h46-6x4j)PYSEC-2026-1656 Published Jan 12, 2026 Updated Oct 28, 2026 Affected 1 pkg Patched 1 / 1 Exploits None indexed Exploitation data as of Nov 9, 2026 Β· OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - A successful exploit gives an attacker total control of the affected component, not partial access. - 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-14279. ## EPSS Exploitation Probability [via FIRST.org β†—](https://www.first.org/epss/) 0.2%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs12th percentile β€” riskier than 12% of all scored CVEsHighest risk 0.00%0.24%0.48%0.72%0.0%0.2%May 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## How urgent is this, really ## Where this sits among everything scored ## Real-World Exposure 1 pkg affected 🐍`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 MLFlow versions up to and including 3.4.0 are vulnerable to DNS rebinding attacks due to a lack of Origin header validation in the MLFlow REST server. This vulnerability allows malicious websites to bypass Same-Origin Policy protections and execute unauthorized calls against REST endpoints. An attacker can query, update, and delete experiments via the affected endpoints, leading to potential data exfiltration, destruction, or manipulation. The issue is resolved in version 3.5.0. ## Affected Packages 1 total 1 fixed Ecosystem Package Vulnerable range Fix 🐍PyPI `mlflow` all versions 3.5.0`pip install --upgrade 'mlflow==3.5.0'` ## Affected Products 1 product Β· 1 configurations Application `mlflow`lfprojects < 3.5.0 range ## 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.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range β€” O3 confirms CVE-2025-14279 is resolved across your whole dependency graph. 3. ### Workarounds If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands. ## Frequently Asked Questions MLFlow versions up to and including 3.4.0 are vulnerable to DNS rebinding attacks due to a lack of Origin header validation in the MLFlow REST server. This vulnerability allows malicious websites to bypass Same-Origin Policy protections and execute unauthorized calls against REST endpoints. An attacker can query, update, and delete experiments via the affected endpoints, leading to potential data exfiltration, destruction, or manipulation. The issue is resolved in version 3.5.0. O3 Security Β· Impact-Aware SCA ### Is CVE-2025-14279 in your dependencies? Find it across PyPI, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)