SummaryAI-written · claude-haiku-5-5AI-written · claude-haiku-5-5Written by a language model from the source data on this page. Not reviewed by a person. Generated 29 Oct 2026.
An absolute path traversal flaw exists in the mlflow/mlflow GitHub repository, in versions prior to 2.5.0. The vulnerability lets an attacker reach files outside the intended directory by supplying absolute paths, and it can be exploited remotely without authentication or user interaction.
Official description · CVE.orgSource dataSource dataCopied from an authoritative feed: NVD, CVE.org, CISA KEV, FIRST EPSS or MITRE CTID mappings, or labelled by the annotators of a published dataset. Copied from CVE.org.
Absolute Path Traversal in GitHub repository mlflow/mlflow prior to 2.5.0.
Priority scorePatchfirst’s 0 to 100 ranking. It adds points for CISA KEV listing, ransomware use, EPSS, threat reports, public exploit code and CVSS. Every CVE page shows the breakdown.Breakdown
31.9 / 100
Exploited
Not confirmed
Reports
0
Tactics
0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Disclosed on 19 Jul 2023. No public exploit code or confirmed exploitation is recorded.
Patch historyEarlier and later CVEs in the same code, in date order. It shows when a fix was bypassed or incomplete and which version finally fixed it.
10 related vulnerabilities in the same code over 20 months. The latest fix listed for mlflow is 2.8.1.
Same bug familyLinked by evidence that a fix failed or the same code was patched again. Oldest first.
This CVECVE-2023-3765Absolute Path Traversal in mlflow/mlflow19 Jul 2023
relatedMedium
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
No techniques linked
No ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.
Am I affected? What do I upgrade to?
From GitHub Security Advisories and OSVSourceSource dataCopied from an authoritative feed: NVD, CVE.org, CISA KEV, FIRST EPSS or MITRE CTID mappings, or labelled by the annotators of a published dataset. GitHub Security Advisories and OSV.
Still affected on this line by CVE-2026-2614 (fixed in 3.10.0, a newer line); CVE-2026-2652 (fixed in 3.10.0, a newer line); CVE-2026-64849 (fixed in 3.15.0, a newer line).
pippip install "mlflow>=2.22.4"
First fixed in 2.5.0 for CVE-2023-3765.
Affected versions
If you run
Upgrade to
All versions before 2.5.0
2.22.4first fix for this CVE: 2.5.0
“Up to” means the second version is the fix and is not affected.