MySQL · Lifecycle Status

MySQL End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all MySQL versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

MySQL 9.7.1 is actively supported. Next EOL: version 8.4 on April 30, 2032.
📅 Get reminded before MySQL 8.4 reaches EOL on April 30, 2032 — alerts 90, 30 & 7 days out.
Google →
Latest Active
9.7.1
9.7 series
Next EOL
8.4
Apr 30, 2032
Active Versions
2
of 16 total
EOL Versions
14
no longer patched
75 / 100
High Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
25/40
Attack Surface
30/30 Critical tier
CISA KEV Exposure
20/20 Yes — 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 →
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 2011201220132014201520162017201820192020202120222023202420252026202720282029203020312032203320345.55.65.78.08.18.28.38.49.09.19.29.39.49.59.69.7TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
5.5 5.5.63 Dec 3, 2010 Dec 31, 2018 2731 days past EOL EOL
5.6 5.6.51 Feb 1, 2013 Feb 28, 2021 1941 days past EOL EOL
5.7 5.7.44 Oct 9, 2015 Oct 31, 2023 966 days past EOL EOL
8.0 LTS 8.0.46 Apr 8, 2018 Apr 30, 2026 54 days past EOL EOL
8.1 8.1.0 Jun 21, 2023 Oct 25, 2023 972 days past EOL EOL
8.2 8.2.0 Oct 12, 2023 Dec 14, 2023 922 days past EOL EOL
8.3 8.3.0 Dec 14, 2023 Apr 10, 2024 804 days past EOL EOL
8.4 LTS 8.4.10 Apr 10, 2024 Apr 30, 2032 2138 days remaining Active
9.0 9.0.1 Jun 7, 2024 Oct 15, 2024 616 days past EOL EOL
9.1 9.1.2 Sep 24, 2024 Jan 21, 2025 518 days past EOL EOL
9.2 9.2.2 Dec 15, 2024 Apr 15, 2025 434 days past EOL EOL
9.3 9.3.2 Mar 31, 2025 Jul 22, 2025 336 days past EOL EOL
9.4 9.4.2 Jul 9, 2025 Oct 21, 2025 245 days past EOL EOL
9.5 9.5.2 Oct 21, 2025 Jan 20, 2026 154 days past EOL EOL
9.6 9.6.1 Jan 20, 2026 Apr 21, 2026 63 days past EOL EOL
9.7 LTS 9.7.1 Apr 21, 2026 Apr 21, 2034 2859 days remaining Active

What does MySQL end of life mean for your organization?

When a version of MySQL reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL MySQL should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL MySQL versions. This is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Need Extended Support?

We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.

Contact Us →
Frequently Asked Questions
What is the end-of-life date for MySQL?
The next MySQL version reaching EOL is 8.4 on April 30, 2032. See the full table above for all version EOL dates.
When is the MySQL support end date?
The next MySQL support end date is April 30, 2032, when version 8.4 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of MySQL?
The latest active version of MySQL is 9.7.1. Always verify against the table above as support windows can change.
What happens when MySQL reaches end of life?
When MySQL reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of MySQL?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL MySQL versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.
Does MySQL track end-of-life by point release (e.g. MySQL 9.7.1, MySQL 9.7.2)?
No — MySQL end-of-life dates apply to the entire 9.7.x release series, not individual point releases. A point release like MySQL 9.7.1 or MySQL 9.7.2 shares the same EOL date as MySQL 9.7. Security patches stop for the entire 9.7.x line on that date, regardless of which patch version you are running. Check the table above for EOL dates by major version series.
Deep Dive
Full Guide
MySQL End of Life: Complete Version Support and EOL Dates

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →