MySQL End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all MySQL versions. Data from endoflife.date, checked against the vendor's own lifecycle pages where we have read them (share on /accuracy). Updated at every deploy.
MySQL 26.10 is supported, with no end-of-life or end-of-support date announced yet. The next MySQL version to reach end of life is 8.4, in April 2032. 20 of 23 tracked MySQL versions are past end of life; the most recent to reach it, 26.7, did so on October 20, 2026. The full MySQL lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 3.23 | 3.23.58 | Jan 17, 2001 | Dec 31, 2006 | 7251 days past EOL | EOL |
| 4.0 | 4.0.30 | Mar 15, 2003 | Sep 30, 2008 | 6612 days past EOL | EOL |
| 4.1 | 4.1.24 | Oct 23, 2004 | Dec 31, 2009 | 6155 days past EOL | EOL |
| 5.0 | 5.0.96 | Oct 24, 2005 | Dec 31, 2011 | 5425 days past EOL | EOL |
| 5.1 | 5.1.73 | Dec 8, 2008 | Dec 31, 2013 | 4694 days past EOL | EOL |
| 5.5 | 5.5.63 | Dec 3, 2010 | Dec 31, 2018 | 2868 days past EOL | EOL |
| 5.6 | 5.6.51 | Feb 1, 2013 | Feb 28, 2021 | 2078 days past EOL | EOL |
| 5.7 | 5.7.44 | Oct 9, 2015 | Oct 31, 2023 | 1103 days past EOL | EOL |
| 8.0 LTS | 8.0.46 | Apr 19, 2018 | Apr 2026 | EOL since April 2026 | EOL |
| 8.1 | 8.1.0 | Jul 18, 2023 | Oct 25, 2023 | 1109 days past EOL | EOL |
| 8.2 | 8.2.0 | Oct 25, 2023 | Jan 16, 2024 | 1026 days past EOL | EOL |
| 8.3 | 8.3.0 | Jan 16, 2024 | Apr 30, 2024 | 921 days past EOL | EOL |
| 8.4 LTS | 8.4.13 | Apr 30, 2024 | Apr 2032 | EOL in April 2032 | Active |
| 9.0 | 9.0.1 | Jul 1, 2024 | Oct 15, 2024 | 753 days past EOL | EOL |
| 9.1 | 9.1.2 | Oct 15, 2024 | Jan 21, 2025 | 655 days past EOL | EOL |
| 9.2 | 9.2.2 | Jan 21, 2025 | Apr 15, 2025 | 571 days past EOL | EOL |
| 9.3 | 9.3.2 | Apr 15, 2025 | Jul 22, 2025 | 473 days past EOL | EOL |
| 9.4 | 9.4.2 | Jul 22, 2025 | Oct 21, 2025 | 382 days past EOL | EOL |
| 9.5 | 9.5.2 | Oct 21, 2025 | Jan 20, 2026 | 291 days past EOL | EOL |
| 9.6 | 9.6.1 | Jan 20, 2026 | Apr 21, 2026 | 200 days past EOL | EOL |
| 9.7 LTS | 9.7.4 | Apr 21, 2026 | Apr 2034 | EOL in April 2034 | Active |
| 26.7 | 26.7.1 | Jul 28, 2026 | Oct 20, 2026 | 18 days past EOL | EOL |
| 26.10 | 26.10.0 | Oct 20, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/mysql)
MySQL release and support pattern
Across the 23 release lines with a published release date, MySQL has shipped a new line roughly every 3 months (median interval). A line typically stays supported for about 2.7 years from its release to its end-of-life date (measured on the 22 lines with both dates published). 3 of the 23 tracked lines are designated long-term support, which is where the longer windows sit.
Of the 23 release lines tracked, 20 are past end of life and 3 are still within support. The newest line, 26.10, was released October 20, 2026. The next scheduled end of life is 8.4 in April 2032 (the vendor names the month only). The longest-supported line currently published is 9.7, to April 2034.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps 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.
Your options when MySQL reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, check whether the vendor or a third party sells extended support with security patches for your MySQL version; coverage varies by product and version. Where it exists it is a bridge, not a permanent solution — plan your migration in parallel.
MySQL has 20 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for MySQL is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."