MySQL Versions: Releases & End of Support Dates

This is a reference list of every MySQL version — the same table our MySQL database support team works from when assessing an install base. It covers MySQL 5.6 through the current 9.x series, with GA dates, premier and extended support end dates under the Oracle lifecycle, and current status. Dates are cross-checked against Oracle's lifetime support policy and endoflife.date/mysql.

MySQL versions list: all releases and support dates

MySQL Community and Enterprise editions follow the Oracle Lifetime Support Policy: LTS releases get five years of premier support and three further years of extended support, roughly eight years total. Innovation releases (the 9.0–9.6 series) are supported only until the next quarterly release ships.

The MySQL release model: LTS and innovation tracks

Oracle changed the release model in 2023, splitting MySQL into two tracks, documented in the official announcement on dev.mysql.com:

• LTS releases ship roughly every two years (8.4 in April 2024, 9.7 in April 2026). Each gets five years of premier support plus three years of extended support. Within an LTS series, patch releases (8.4.1, 8.4.2, …) contain bugfixes and security fixes only — no new features, no behavior changes.
• Innovation releases ship quarterly (8.1, 8.2, 8.3, then 9.0 through 9.6). Each carries new features and is production-grade, but is supported only until the next quarterly release. Running the innovation track means upgrading roughly every three months.

MySQL 8.0 predates this model. From 8.0.34 onward it moved to bugfix-only status as a de facto pre-LTS branch, and its extended support window closed in April 2026. The innovation series that followed it (8.1–8.3) rolled into 8.4 LTS, and the 9.0–9.6 innovation series rolled into 9.7 LTS.

MySQL 8.0 end of life

MySQL 8.0 reached end of life on April 30, 2026. Premier support had already ended a year earlier, on April 30, 2025; the final year was extended support (security fixes only). The last release in the series was 8.0.46 (April 2026).

Past that date, an 8.0 server receives:

• No security patches. New CVEs in the 8.0 codebase remain unfixed. Oracle publishes quarterly Critical Patch Updates for supported versions only.
• No bugfix releases. 8.0.46 is the final build.
• No support cases. Oracle sustaining support answers questions about existing fixes but produces no new ones.

MySQL 8.0 shipped in 2018 and is the most widely deployed version in production, which makes this the largest MySQL migration event since 5.7 retired. The upgrade target is 8.4 LTS; the jump is smaller than 5.7 to 8.0 was, since 8.4 is the same major architecture with deprecated features removed (mysql_native_password default authentication being the most common breakage). If you are still on 8.0, the upgrade is overdue, not upcoming.

Upgrade paths

Oracle supports upgrading one LTS step at a time; skipping an LTS version is not a supported in-place path, per the upgrade paths documentation:

Downgrades are not supported in any direction after 8.0 — once the data dictionary is upgraded, the only way back is restoring a backup. Take a full backup before any version change. Within an LTS series (8.4.10 → 8.4.11), in-place patching is routine and reversible risk is minimal.

How to check your MySQL version

From a client session:

SELECT VERSION();

From the shell, without logging in:

mysql --version

The output maps directly to the table above: 8.0.x is end of life, 8.4.x is LTS (supported to April 2032), 9.7.x is the current LTS. Anything reporting 5.x has been out of support for years. Server platform requirements per version are listed on mysql.com supported platforms. Installers for current versions are collected in our MySQL download guide.

Still running MySQL 5.7

MySQL 5.7 exited extended support on October 31, 2023, at release 5.7.44. Unlike SQL Server, there is no paid extended-security-update program for the Community edition: past the extended support date, no patch channel exists at any price. Surveys of production fleets continue to show a large share of 5.7 instances years after that date, mostly pinned by application compatibility — old ORMs, removed SQL modes, and the authentication plugin change in 8.0.

The options are narrow: upgrade to 8.0 as an intermediate hop and continue to 8.4, migrate the workload to a managed service that still runs patched 5.7-compatible builds (some cloud providers backport fixes to their own forks), or accept an unpatched database server — which fails PCI DSS, HIPAA, and most cyber-insurance requirements outright. Isolation (separate VLAN, no internet egress, restricted accounts) reduces exposure but does not change the audit finding.

MySQL and MariaDB version numbers do not correspond

MariaDB forked from MySQL 5.5 in 2009 and its version numbers diverged completely after 10.0 — MariaDB 11.x is not newer than MySQL 9.x, and the two have separate lifecycles; see our MariaDB overview for that track.

FAQ

What is the latest version of MySQL?

MySQL 9.7 is the latest LTS release, generally available since April 21, 2026, with support through April 2034. MySQL 8.4 remains supported through April 2032.

Is MySQL 8.0 still supported?

No. MySQL 8.0 reached end of life on April 30, 2026. The supported upgrade path is 8.0 to 8.4 LTS.

When does MySQL 8.4 end of life happen?

Premier support for 8.4 ends April 30, 2029; extended support ends April 30, 2032.

How long is a MySQL LTS version supported?

Eight years: five years of premier support and three years of extended support under the Oracle Lifetime Support Policy. Innovation releases are supported only until the next quarterly release.