MLflow has a Local File Read/Path Traversal bypass

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2024-3848: 43.28% estimated exploitation activity in the next 30 days; percentile 98.73 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A path traversal vulnerability exists in mlflow/mlflow version 2.11.0, identified as a bypass for the previously addressed CVE-2023-6909. The vulnerability arises from the application's handling of artifact URLs, where a '#' character can be used to insert a path into the fragment, effectively skipping validation. This allows an attacker to construct a URL that, when processed, ignores the protocol scheme and uses the provided path for filesystem access. As a result, an attacker can read arbitrary files, including sensitive information such as SSH and cloud keys, by exploiting the way the application converts the URL into a filesystem path. The issue stems from insufficient validation of the fragment portion of the URL, leading to arbitrary file read through path traversal.

Published by the source

16 May 2024, 09:33 UTC

Last modified by the source

8 Apr 2025, 22:31 UTC

Source last checked

26 Oct 2026, 13:31 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-rfqq-wq6w-72jm

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-rfqq-wq6w-72jm

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-3848

Advisory: MLflow has a Local File Read/Path Traversal bypass
IDs: CVE-2024-3848, GHSA-rfqq-wq6w-72jm
Record: https://patchnext.com/advisories/cve-2024-3848 (revision 2, source checked 26 Oct 2026, 13:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mlflow 2.12.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI mlflow: affected >= 2.9.2, < 2.12.1; fixed in 2.12.1

## Suggested inspection (read-only)
- `python -m pip show mlflow`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mlflow.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-rfqq-wq6w-72jm (OSV record GHSA-rfqq-wq6w-72jm lists affected ranges: PyPI mlflow >=2.9.2 <2.12.1 (fixed))
- Verified: https://github.com/advisories/GHSA-rfqq-wq6w-72jm (GitHub-reviewed advisory GHSA-rfqq-wq6w-72jm lists affected ranges: PyPI mlflow >=2.9.2 <2.12.1)

Commands are suggestions: review each one before running it.