Local File Inclusion (LFI) via Scheme Confusion in mlflow/mlflow
Noroxi assessment
Priority: Monitor (action score 37/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.73% (FIRST EPSS); higher than 53.1% 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 (PyPI) 2.10.0.
Low priority for now. Upgrade to mlflow (PyPI) 2.10.0 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
mlflow/mlflow is vulnerable to Local File Inclusion (LFI) due to improper parsing of URIs, allowing attackers to bypass checks and read arbitrary files on the system. The issue arises from the 'is_local_uri' function's failure to properly handle URIs with empty or 'file' schemes, leading to the misclassification of URIs as non-local. Attackers can exploit this by crafting malicious model versions with specially crafted 'source' parameters, enabling the reading of sensitive files within at least two directory levels from the server's root.
- Published
- Apr 15, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- CWE-29
Report tools
Action score
37
Monitor
Low priority for now.
- CVSS
- 37 / 40 · 9.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 9.3
- CNA · @huntr_ai
- 9.3
- agree
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/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
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| lfprojects | mlflow | cpe:2.3:a:lfprojects:mlflow |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- lfprojects mlflowbefore 2.10.0
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.10.0affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| PyPI | mlflow | before 2.10.0 | 2.10.0 |
Same product
lfprojects: all recordsOther 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)KEV70This week
- CVE-2023-3765Absolute Path Traversal in mlflow/mlflow60This week
- CVE-2023-1177Path Traversal: '\..\filename' in mlflow/mlflow60This week
- CVE-2023-6909Path Traversal: '\..\filename' in mlflow/mlflow57Plan
- CVE-2023-6018MLflow Arbitrary File Write53Plan
- CVE-2025-11201MLflow Tracking Server Model Creation Directory Traversal Remote Code Execution Vulnerability47Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| PyPI:mlflow | 2.10.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
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.
No dated events beyond publication.
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 researchersFinders, 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-1177388 days apartPath Traversal: '\..\filename' in mlflow/mlflow60This week
- CVE-2023-6909119 days apartPath Traversal: '\..\filename' in mlflow/mlflow57Plan
- CVE-2024-384831 days apartPath Traversal Bypass in mlflow/mlflow43Plan
- CVE-2023-2780334 days apartPath Traversal: '\..\filename' in mlflow/mlflow41Plan
- CVE-2023-6975117 days apartPath Traversal: '\..\filename'40Plan
- CVE-2024-292852 days apartLocal File Inclusion (LFI) via URI Fragment Parsing in mlflow/mlflow37Monitor
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
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- Low
- 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:C/C:H/I:L/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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.