{"uuid": "8cd36440-f3a1-4720-991b-e1cb340e7cf5", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "GHSA-3p64-6gvh-82v5", "type": "seen", "source": "https://gist.github.com/alon710/bb0c1f0112166e936833a909d435a77a", "content": "# CVE-2026-69146: CVE-2026-69146: Missing Authorization Bypass in MLflow Basic Authentication Middleware\n\n> **CVSS Score:** 6.5\n> **Published:** 2026-08-17\n> **Full Report:** https://cvereports.com/reports/CVE-2026-69146\n\n## Summary\nThis technical report details a missing authorization vulnerability (CVE-2026-69146 / GHSA-3p64-6gvh-82v5) affecting the MLflow platform from version 3.13.0 to 3.15.0. When MLflow is configured with the built-in basic-auth plugin, authenticated users can bypass run-level UPDATE authorization checks, enabling unauthorized dataset and model lineage metadata injection.\n\n## TL;DR\nAn authorization bypass vulnerability in MLflow's basic-auth middleware allows authenticated users to inject arbitrary dataset records into other users' runs without UPDATE permissions.\n\n## Exploit Status: POC\n\n## Technical Details\n\n- **CWE ID**: CWE-862\n- **Attack Vector**: Network (AV:N)\n- **CVSS**: 6.5\n- **EPSS Status**: Not Populated\n- **Impact**: High Integrity (I:H)\n- **Exploit Status**: POC / Test-Suite Verified\n- **KEV Status**: Not Listed\n\n## Affected Systems\n\n- MLflow Platform Tracking Server\n- **MLflow**: >= 3.13.0, < 3.15.0 (Fixed in: `3.15.0`)\n\n## Mitigation\n\n- Upgrade to MLflow version 3.15.0 or later to integrate LogInputs and LogOutputs with the tracking server access control middleware.\n- Implement network boundary controls to limit access to the MLflow tracking port.\n- Apply reverse proxy or API gateway rules to filter and deny untrusted external traffic to the log-inputs and log-outputs REST endpoints.\n\n**Remediation Steps:**\n1. Verify the current MLflow version using package management tools or API server banners.\n2. Upgrade MLflow installations via 'pip install --upgrade mlflow>=3.15.0' or rebuild target containers using the updated image base.\n3. Ensure MLflow tracking servers are configured behind a web application firewall or reverse proxy.\n4. Configure log alerting for HTTP POST requests directed to /api/2.0/mlflow/runs/log-inputs originating from unexpected source networks.\n\n## References\n\n- [NVD CVE-2026-69146 Detail](https://nvd.nist.gov/vuln/detail/CVE-2026-69146)\n- [GitHub Security Advisory GHSA-3p64-6gvh-82v5](https://github.com/mlflow/mlflow/security/advisories/GHSA-3p64-6gvh-82v5)\n- [MLflow Security Fix Pull Request #24291](https://github.com/mlflow/mlflow/pull/24291)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-69146) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-08-18T00:01:16.137907Z"}