HighVulnerability
CVE-2024-3848: mlflow/mlflow path traversal in artifact URL handling via fragment
- Source
- NVD(opens in a new tab)
- Identifier
- CVE-2024-3848
- Published
- Record updated
- Affected
- mlflow >= 2.9.2, < 2.12.1
- Fixed in
- 2.12.1
- released April 16, 2024, 29 days before disclosure
- Known exploitation
- Not listed in the CISA Known Exploited Vulnerabilities catalog at the last check.
- EPSS
- 43.3%
Summary
A path traversal flaw in mlflow/mlflow version 2.11.0 bypasses the earlier fix for CVE-2023-6909. The application mishandles artifact URLs, where a '#' character lets an attacker insert a path into the fragment and skip validation, so the protocol scheme is ignored. An attacker can read arbitrary files, including SSH and cloud keys.
Mitigation
The source does not state a fix yet. Check the original advisory for updates.
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