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.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 5.5 | 5.5.63 | Dec 3, 2010 | Dec 31, 2018 | 2749 days past EOL | EOL |
| 5.6 | 5.6.51 | Feb 1, 2013 | Feb 28, 2021 | 1959 days past EOL | EOL |
| 5.7 | 5.7.44 | Oct 9, 2015 | Oct 31, 2023 | 984 days past EOL | EOL |
| 8.0 LTS | 8.0.46 | Apr 8, 2018 | Apr 30, 2026 | 72 days past EOL | EOL |
| 8.1 | 8.1.0 | Jun 21, 2023 | Oct 25, 2023 | 990 days past EOL | EOL |
| 8.2 | 8.2.0 | Oct 12, 2023 | Dec 14, 2023 | 940 days past EOL | EOL |
| 8.3 | 8.3.0 | Dec 14, 2023 | Apr 10, 2024 | 822 days past EOL | EOL |
| 8.4 LTS | 8.4.10 | Apr 10, 2024 | Apr 30, 2032 | 2120 days remaining | Active |
| 9.0 | 9.0.1 | Jun 7, 2024 | Oct 15, 2024 | 634 days past EOL | EOL |
| 9.1 | 9.1.2 | Sep 24, 2024 | Jan 21, 2025 | 536 days past EOL | EOL |
| 9.2 | 9.2.2 | Dec 15, 2024 | Apr 15, 2025 | 452 days past EOL | EOL |
| 9.3 | 9.3.2 | Mar 31, 2025 | Jul 22, 2025 | 354 days past EOL | EOL |
| 9.4 | 9.4.2 | Jul 9, 2025 | Oct 21, 2025 | 263 days past EOL | EOL |
| 9.5 | 9.5.2 | Oct 21, 2025 | Jan 20, 2026 | 172 days past EOL | EOL |
| 9.6 | 9.6.1 | Jan 20, 2026 | Apr 21, 2026 | 81 days past EOL | EOL |
| 9.7 LTS | 9.7.1 | Apr 21, 2026 | Apr 21, 2034 | 2841 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.
MySQL has 14 versions past end of life — security patches have stopped, but CVE disclosures haven't. Tell us what you run and we'll match you with a vetted extended-support provider within 1 business day. Free, no obligation.
Get My Support Options →