MLflow 2 · Version Status

MLflow 2 End of Life Date

MLflow 2 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (github.com); the source of each date is on the product page.

⚠ MLflow 2 is past end of life. This version no longer receives security patches. Past EOL — migrate to a supported version immediately.
EOL Date
date not published
Past EOL
Latest Release
2.22.5
Standard release
Release Date
Nov 15, 2022
MLflow 2 series
Where these dates come from
ReleaseNov 15, 2022Our catalog, built from the vendor pages · github.commedium · 1 source agrees
Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale. How we source dates.
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

MLflow 2 was released on November 15, 2022. Its most recent patch is 2.22.5, published May 12, 2026.

← MLflow 1 All MLflow versions MLflow 3 →
65 / 100
High Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
35/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
Recommended upgrade path
MLflow 3
Latest release: 3.18.0 · EOL: Supported
View full MLflow timeline →
Extended Support
Extended MLflow 2 support options

Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.

Compare Options →
All MLflow Versions
VersionLatestEOL DateStatus
1 1.30.1 Supported EOL
→ 2 2.22.5 Supported EOL
3 3.18.0 EOL Active

What does MLflow 2 end of life mean?

When MLflow 2 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running MLflow 2 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to MLflow 3 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does MLflow 2 reach end of life?
MLflow 2 has already reached end of life, though the vendor has not published an exact date.
Is MLflow 2 still supported?
No. MLflow 2 reached end of life on an unpublished date and is no longer receiving security patches.
What should I upgrade to from MLflow 2?
The recommended upgrade from MLflow 2 is MLflow 3 — the latest actively supported version. Check the MLflow full timeline for all supported versions.
What are the security risks of running MLflow 2 past EOL?
Since MLflow 2 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL MLflow should migrate immediately or implement compensating controls.
Deep Dive
Guide to MLflow 2
MLflow 2.x: Actively Exploited (CVE-2026-64849), Fixed Only in 3.15 — and Never Declared End of Life
→
Data from the vendor's own lifecycle pages (github.com) · Generated at build time · How we source data →