Skip to content
Noroxi
CVE-2024-2928· NVD / CVE Program· CNA @huntr_ai

Local File Inclusion (LFI) via URI Fragment Parsing in mlflow/mlflow

Noroxi assessment

Priority: Monitor (action score 37/100)

  • A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 21.8% (FIRST EPSS); higher than 97.6% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: mlflow mlflow/mlflow 2.11.3.

Low priority for now. Upgrade to mlflow mlflow/mlflow 2.11.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

A Local File Inclusion (LFI) vulnerability was identified in mlflow/mlflow, specifically in version 2.9.2, which was fixed in version 2.11.3. This vulnerability arises from the application's failure to properly validate URI fragments for directory traversal sequences such as '../'. An attacker can exploit this flaw by manipulating the fragment part of the URI to read arbitrary files on the local file system, including sensitive files like '/etc/passwd'. The vulnerability is a bypass to a previous patch that only addressed similar manipulation within the URI's query string, highlighting the need for comprehensive validation of all parts of a URI to prevent LFI attacks.

HighCVSS 7.5 · v3.1—Proof of concept Fix available
Published
Jun 6, 2024
Updated
Jun 17, 2026
EPSS
21.8% · 97th percentile

Report tools

JSON

Action score

37

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
7 / 30 · 21.8%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.5
CNA · @huntr_ai
7.5
agree

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-2928

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for lfprojects records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
lfprojectsmlflow

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • lfprojects mlflowbefore 2.11.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (@huntr_ai). Independent of NVD's CPE analysis and usually ahead of it.

  • mlflow mlflow/mlflow

    • unspecified and later · before 2.11.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
PyPImlflowbefore 2.11.32.11.3

Same product

lfprojects: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-64849MLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebinding)KEV
    70This week
  • CVE-2023-3765Absolute Path Traversal in mlflow/mlflow
    60This week
  • CVE-2023-1177Path Traversal: '\..\filename' in mlflow/mlflow
    60This week

Published before and after this one in the same product

  • ← EarlierCVE-2024-37061Jun 4, 2024 · Remote Code Execution can occur in versions of the MLflow platform running version 1.11.0 or newer, enabling a maliciously crafted MLproject
    35Monitor
  • ← EarlierCVE-2024-0520Jun 6, 2024 · Remote Code Execution due to Full Controlled File Write in mlflow/mlflow
    36Monitor
  • Later →CVE-2024-3099Jun 6, 2024 · Denial of Service and Data Model Poisoning via URL Encoding in mlflow/mlflow
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
mlflow mlflow/mlflow2.11.3 · descriptionVendor (CNA)
PyPI:mlflow2.11.3Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Nuclei detection template ×1
  • Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Nuclei detection templateNuclei template CVE-2024-2928 —
Proof-of-concept repository on GitHubstars:32024-11-08
Proof-of-concept repository on GitHubstars:12025-12-04

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoC+154 d
  3. TodayOct 25, 2026+871 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2023-1177440 days apartPath Traversal: '\..\filename' in mlflow/mlflow
    60This week
  • CVE-2023-6909171 days apartPath Traversal: '\..\filename' in mlflow/mlflow
    57Plan
  • CVE-2024-384821 days apartPath Traversal Bypass in mlflow/mlflow
    43Plan
  • CVE-2023-2780386 days apartPath Traversal: '\..\filename' in mlflow/mlflow
    41Plan
  • CVE-2023-6975169 days apartPath Traversal: '\..\filename'
    40Plan
  • CVE-2024-357352 days apartLocal File Inclusion (LFI) via Scheme Confusion in mlflow/mlflow
    37Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-29 · Path Traversal: '\..\filename'

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records