# What is CVE-2024-3848?

> 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.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2024-3848

## At a glance

- **Verdict:** Fix this soon. Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
- **Precursor Intelligence risk score:** 50 out of 100 (Medium); action: Plan remediation. Kept up to date as the evidence changes.
- **Severity:** High (CVSS 7.5 out of 10)
- **Known to be exploited:** No, not on the list of flaws known to be exploited today
- **Chance of use in the next 30 days:** 43% (latest exploit-likelihood forecast)
- **Published:** 16 May 2024
- **Record last updated:** 17 June 2026
- **Main product:** Mlflow from Lfprojects
- **Affected products:** 1

## 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.

### The official 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.

### What kind of flaw is it?

- CWE-29: Path Traversal: '\\..\\filename'
- CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

### How an attack on it works

- Where an attacker can be: Anywhere on the internet
- How hard it is to pull off: Easy: no special conditions
- Login needed first: No login needed
- Does someone have to click: No, nobody has to do anything
- What an attacker gets: Can 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.

Exploit likelihood over the last 7 days: 43%, 43%, 43%, 43%, 43%, 43%, 43%.

### Timeline

- 16 May 2024: Published
- 25 June 2025: Exploit likelihood jumped
- 19 November 2025: Exploit likelihood fell
- 17 June 2026: Record last updated

### How Precursor Intelligence ranks it

CVE-2024-3848 scores **50 out of 100 (Medium)**, with the action "Plan remediation".

Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less:

- Evidence it is being exploited: biggest factor
- How severe it is: strong factor
- How widely exposed it is: smaller factor
- Threat activity around it: smaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it.

## Who is affected by CVE-2024-3848?

The published record lists 1 product. Versions are as published: "before 2.12.1" means every version up to, but not including, 2.12.1.

- [Mlflow](https://www.precursorintelligence.com/product/lfprojects/mlflow) by [Lfprojects](https://www.precursorintelligence.com/vendors/lfprojects) (Application): before 2.12.1

## How do I fix CVE-2024-3848?

1. **Check whether you run it.** Compare 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.
2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisory first in the list.
3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
4. **Keep an eye on it.** Track 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.

### References

- [github.com](https://github.com/mlflow/mlflow/commit/f8d51e21523238280ebcfdb378612afd7844eca8) (Patch)
- [huntr.com](https://huntr.com/bounties/8d5aadaa-522f-4839-b41b-d7da362dd610) (Exploit, Issue tracking, Third-party advisory)

## Questions

### What is CVE-2024-3848?

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.

### How serious is CVE-2024-3848?

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.

### Is CVE-2024-3848 being exploited?

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.

### Which versions does CVE-2024-3848 affect?

For Mlflow from Lfprojects: before 2.12.1.

### How do I fix CVE-2024-3848?

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.

## Does CVE-2024-3848 affect you?

Precursor Intelligence keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.precursorintelligence.com/register
Book a demo: https://www.precursorintelligence.com/contact