What is CVE-2024-3848?A high-severity flaw in Mlflow, explained.
CVE-2024-3848 is a high-severity flaw (CVSS 7.5) in Mlflow from Lfprojects, published on 16 May 2024. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 43%. If you run an affected version, plan in the vendor’s fix.
Published 16 May 2024. Record last updated 17 June 2026. We keep this page's data up to date.
What is CVE-2024-3848? In plain terms.
It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data.
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.
What kind of flaw is it?
- CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CWE-29Path Traversal: '\..\filename'
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read data
Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Is CVE-2024-3848 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 43%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Exploit likelihood jumped
- Exploit likelihood fell
- Record last updated
CVE-2024-3848 scores 50. Action: Plan remediation.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2024-3848 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2024-3848? One product.
The published record lists 1 product from 1 vendor. Versions are shown as published: "before 2.12.1" means every version up to, but not including, 2.12.1. If you run one of these, check your version, then go to the fix below.
- Application
Mlflow
by Lfprojects
Affected versionsbefore 2.12.1
How do I fix CVE-2024-3848? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
Does CVE-2024-3848 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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 a...
- Matched to
- Mlflow on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2024-3848 is a high-severity flaw in Mlflow from Lfprojects, published on 16 May 2024. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data.
It scores 7.5 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2024-3848 is 50 out of 100, which is Medium. Its action is "Plan remediation". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 43%. That can change at any time, which is why we keep watching.
For Mlflow from Lfprojects: before 2.12.1.
Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.