CVE-2024-3848Mlflow Path Traversal
MLflow has a Local File Read/Path Traversal bypass
Published May 16, 2024 · Updated Oct 28, 2026 · Also known as BIT-mlflow-2024-3848, GHSA-rfqq-wq6w-72jm, PYSEC-2024-244
Key Facts
Patch immediately- CVE-2024-3848 is a high-severity vulnerability (CVSS 7.5 v3.1) affecting Mlflow (Lfprojects), mlflow/mlflow.
- It is exploited in the wild, listed in CIRCL KEV, Industry KEV feed since Oct 27, 2026. A public exploit is reported by tracking sources, but no code link is listed yet.
- EPSS estimates a 43% probability of exploitation in the next 30 days.
- Fixed versions are available, including Mlflow 2.12.1, Mlflow f8d51e21523238280ebcfdb378612afd7844eca8, mlflow/mlflow 2.12.1.
- Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Scores
CVSS v3.1
7.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS (30-day exploit likelihood)
43%
Higher than 98.7% of all scored CVEs
Exploit maturity
Exploited (KEV)
ATLAS score
55/100
Publication score, see How it works
Exploitation Verdict
KEV listed
Oct 27, 2026
894 days after publication
Federal due date
None
No federal due date
Ransomware use
Not reported
Attributed actors
None named
Exploit & Defence Guidance
Exploit maturity
Exploited (KEV)
Public exploit code
0
Proof-of-concept links
In-the-wild evidence
2
Reports of active use
Advisories And Exploit References
Description
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.
Known-Exploited Catalog Listings
| Catalog | Added | Remediation due | Ransomware use |
|---|---|---|---|
| CIRCL KEV | Oct 27, 2026 | n/a | Not reported |
| Industry KEV feed | Oct 27, 2026 | n/a | Not reported |
Affected Products
4 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| MlflowLfprojects | >= 2.9.2 | 2.12.1 |
| mlflow/mlflow | >= unspecified | 2.12.1 |
Patched Releases
Mlflow
2.12.1, f8d51e21523238280ebcfdb378612afd7844eca8
mlflow/mlflow
2.12.1
Timeline
Publicly disclosed
May 16, 2024
Added to CIRCL KEV
Oct 27, 2026
Added to Industry KEV feed
Oct 27, 2026
Last updated
Oct 28, 2026
Weakness Type
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CWE-29 Path Traversal: '\..\filename'
References
- advisorycve.org · CVERecord
- advisorynvd.nist.gov · CVE-2024-3848
- advisoryGHSA advisory
- exploitVulnCheck exploitation report
- articlegithub.com · f8d51e2
FAQ
Common Questions.
A path traversal vulnerability exists in mlflow/mlflow version 2.11.0, identified as a bypass for the previously addressed CVE-2023-6909.
Affected: Mlflow (Lfprojects) versions >= 2.9.2; mlflow/mlflow versions >= unspecified. The full list is in the CVE brief.
It is exploited in the wild, listed in CIRCL KEV, Industry KEV feed since Oct 27, 2026.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
A public exploit is reported by tracking sources, but no code link is listed yet.
Fixed versions are available, including Mlflow 2.12.1, Mlflow f8d51e21523238280ebcfdb378612afd7844eca8, mlflow/mlflow 2.12.1.
Brandefense priority: patch immediately, because it is listed as exploited in the wild.
Is CVE-2024-3848 On Your Attack Surface?
Brandefense matches it against the products discovered on your perimeter and opens a finding the day a CVE like this is listed.
Request A Demo