MySQL 8.0 end of life: ended 30 April 2026, and your options
MySQL 8.0 EOL was 30 April 2026, when Oracle's Extended Support for the line ended. The final release was 8.0.46, on 21 April 2026, and Oracle directs users to 8.4 LTS or an Innovation release. No further community 8.0 builds will ship, so security fixes released after that date are not available for 8.0 from Oracle.
What now
Which vendors provide MySQL 8.0 security patches now that support has ended?
MySQL 8.0 End of Life: Upgrade, Switch or Patch- End of life
- 30 April 2026
- Released
- Apr 2018
- Final release
- 8.0.46 (21 April 2026)
- Successor
- MySQL 8.4 LTS, then 9.7 LTS
Date published by Oracle Lifetime Support Policy and MySQL 8.0 release notes. We do not publish a lifecycle date we cannot source. End-of-life dates checked on endoflife.date and the Amazon RDS for MySQL version page on 22 October 2026; Azure dates as of 7 October 2026. Oracle's Lifetime Support Policy (effective 13 November 2026) and the MySQL release notes checked on 15 November 2026.
Last reviewed
What actually stops on 30 April 2026
- Community releases on the 8.0 line. Oracle's quarterly Critical Patch Updates now ship fixes for 8.4, 9.7 and the Innovation track only.
- Security fixes for vulnerabilities found after April 2026. Amazon's RDS Extended Support build 8.0.46-RDS.20260908, released on 23 September 2026, lists 31 CVE fixes that no community 8.0 release carries.
- Bug fixes, including fixes for crashes and InnoDB corruption, for anything reported against 8.0 after the final release.
- Free standard support on managed services: Amazon RDS moved 8.0 to paid Extended Support on 1 August 2026, and Azure Database for MySQL does the same on 1 February 2027.
What actually breaks in the upgrade
8.0 goes to 8.4 first, not straight to 9.7
MySQL does not allow skipping an LTS series. An 8.0 server upgrades to 8.4, and only then to 9.7. Run MySQL Shell's upgrade checker against each server before the change window; it reports removed syntax, changed defaults and objects that block the upgrade.
Authentication is the usual blocker
From 8.4.0, the deprecated mysql_native_password plugin is no longer enabled by default, and the default_authentication_plugin variable is gone in favour of authentication_policy. Accounts and older client libraries that still rely on mysql_native_password stop connecting unless you enable the plugin or move the accounts to caching_sha2_password first.
Replication scripts use statements that no longer exist
MySQL 8.4 removed CHANGE MASTER TO, START SLAVE, STOP SLAVE, RESET MASTER and SHOW MASTER STATUS. Their replacements, such as CHANGE REPLICATION SOURCE TO and START REPLICA, work on 8.0.23 and later, so failover tooling and runbooks can be changed before the upgrade rather than during it.
MySQL 8.0, 8.4 and 9.7 compared
MySQL 8.0 is the only one of these lines past end of life. 8.4 and 9.7 are both LTS series under Oracle's Lifetime Support Policy, which gives five years of Premier Support and three of Extended Support; 9.7 is the last line numbered the old way, and Innovation releases now use YY.M numbers, such as 26.10.
MySQL release lines, Oracle Lifetime Support Policy effective 13 November 2026
| Line | Track | First GA | Premier Support ends | Extended Support ends | Latest release (15 Nov 2026) | From 8.0 |
|---|---|---|---|---|---|---|
| 8.0 | Previous series | April 2018 | April 2025 | April 2026 (ended) | 8.0.46, 21 April 2026 (final) | Where you are now |
| 8.4 | LTS | 30 April 2024 | April 2029 | April 2032 | 8.4.13, 20 October 2026 | Direct upgrade; the supported next step |
| 9.7 | LTS | 21 April 2026 | April 2031 | April 2034 | 9.7.4, 20 October 2026 | Via 8.4; an LTS series cannot be skipped |
| Innovation (26.7, 26.10) | Innovation | 26.7 on 28 July 2026 | Supported until the next Innovation release | Not applicable | 26.10.0, 20 October 2026 | Not an upgrade target for a stable estate |
Sources: Oracle Lifetime Support Policy (oracle.com), the MySQL release notes and the MySQL 9.7 reference manual section on Innovation and LTS releases, all checked on 15 November 2026. Release dates for 8.4.13, 9.7.4 and 26.10.0 are from the release notes.
CVE fixes since MySQL 8.0 ended
MySQL 8.0 ended on 30 April 2026 with 8.0.46, and Oracle has released no 8.0 build since. In the five months after, Amazon published two RDS Extended Support builds of 8.0.46 that between them list 32 distinct CVE fixes. A self-managed 8.0.46 server has none of them.
CVE fixes published for MySQL 8.0 after end of life
| Build | Released | CVEs fixed | Available to |
|---|---|---|---|
| 8.0.46-RDS.20260624 | 15 July 2026 | 1 | Amazon RDS Extended Support customers |
| 8.0.46-RDS.20260908 | 23 September 2026 | 31 | Amazon RDS Extended Support customers |
| Oracle community 8.0 releases after 8.0.46 | None | 0 | No one |
Source: the Amazon RDS Extended Support release lists on the RDS for MySQL version page, which name each CVE fixed per build; checked 22 October 2026. Counts are CVE identifiers on that page, so they are a floor for the line, not a full count of Oracle's advisories.
Has Oracle patched MySQL since 8.0 ended?
Yes, on 8.4 and 9.7 only. Oracle's July and October 2026 Critical Patch Updates carry 152 new security patches for Oracle MySQL, 121 of them for MySQL Server, and neither advisory lists 8.0 as an affected version, because Oracle's advisories cover supported versions only. No 8.0 build contains any of them. 17 of the 121 Server patches carry an Oracle CVSS score of 7.0 or higher, 2 of those at 9.0 or above.
Oracle Critical Patch Updates for MySQL, read on oracle.com on 17 November 2026
| Advisory | MySQL patches (all products) | MySQL Server patches | Server patches rated 7.0 or higher | Lines listed for MySQL Server |
|---|---|---|---|---|
| April 2026 | 34 | 27 | 1 | 8.0, 8.4 and Innovation 9.x |
| July 2026 | 54 | 41 | 4 | 8.4 and 9.7 |
| October 2026 | 98 | 80 | 13 | 8.4, 9.7 and Innovation 26.7 |
Source: the text-form MySQL risk matrix in each Oracle Critical Patch Update advisory (oracle.com/security-alerts), counted on 17 November 2026; every Server CVE in the 2026 advisories was also checked as published on the CVE Program API. Scores are Oracle's CVSS 3.1 base scores. Oracle's Critical Patch Updates list 8.0 only up to the April advisory, so the counts are what an 8.0.46 server has not received, not a count of flaws proven to affect it. MySQL Cluster, Connectors, Router and Enterprise Backup rows are in the all-products column only.
Three ways forward from MySQL 8.0
Upgrade to 8.4 LTS, switch engine, or stay on 8.0 with patched builds. The upgrade is the default answer and the right one for most estates; the options table above sets out what each route asks of you. Switching to PostgreSQL is a migration OSSeva runs end to end, from assessment to cutover, with the new cluster supported from day one. Staying on 8.0 is a holding position that buys time for either move.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Upgrade to 8.4 LTS | The supported next step, with Premier Support to April 2029. | Scales with server count, client drivers and replication tooling | Engineering time | The right answer for most estates. Plan the later move to 9.7 at the same time. |
| Move to PostgreSQL or MariaDB | A different engine. OSSeva runs MySQL to PostgreSQL migrations and supports the new cluster from day one; MariaDB is the closest MySQL-compatible engine. | Scales with schema size, stored code, data volume and downtime window | Services engagement, then a subscription priced per cluster | Worth it when PostgreSQL or MariaDB is already the direction for the estate. Otherwise an upgrade to 8.4 is less work. |
| Managed-service extended support | Stay on 8.0 on Amazon RDS or Azure Database for MySQL under the provider's paid programme. | None | Per vCPU or vCore hour on top of the instance | Buys time on that service only. It does not cover MySQL you run yourself. |
| OSSeva patched 8.0 builds | Signed 8.0 Community builds with security fixes backported, on your own servers and Kubernetes. Critical CVEs within 48 hours, High within 7 days. | Starts from your current version | Subscription, priced per cluster | Keeps self-managed 8.0 servers patched while the move to 8.4 is planned and rehearsed. |
| Stay on 8.0.46 unpatched | No fixes for anything found after April 2026. | None | Zero now | Every quarterly Oracle advisory widens the gap, and scanners will flag each one. |
What OSSeva does for MySQL 8.0
OSSeva patches this line
OSSeva backports security fixes to MySQL 8.0 Community Edition and ships signed DEB and RPM packages, tarballs and container images on the Patch, Assure and Operate tiers. Assure adds the 8.4 upgrade plan and an authentication review; Operate runs the upgrade replica by replica. Enterprise-only components such as Enterprise Backup or Enterprise Firewall are not part of these builds.
Need 24/7 MySQL support while you upgrade? AceMQ, our sister company, provides it.
MySQL extended supportWhat your auditor will say
The database is a system component in its own right. An unsupported MySQL version with no patch source is a finding; a documented third-party patch stream is the usual remediation.
Auditors ask for evidence that production systems receive security fixes. A MySQL line past end of life fails that test unless another supplier ships the fixes and can show which CVEs they close.
For EU financial entities, the ICT risk and third-party provisions apply when a critical service depends on a database with no support arrangement in place.
When is MySQL 8.0 EOL?
MySQL 8.0 reached end of life on 30 April 2026, when Oracle's Extended Support for the line ended. Premier Support had ended in April 2025. The last release, 8.0.46, shipped on 21 April 2026.
What are the consequences of MySQL 8.0 end of life?
Oracle ships no more 8.0 releases, so security and bug fixes published after April 2026 do not reach 8.0. Vulnerability scanners keep flagging new MySQL CVEs, audits treat an unsupported database as a finding, and Amazon RDS and Azure charge for extended support.
Is MySQL 8.0 still supported on AWS?
Only under paid RDS Extended Support. Standard support for 8.0 on Amazon RDS ended on 31 July 2026, and Extended Support runs from 1 August 2026 to 31 July 2029.
Is MySQL 8.0 still supported on Azure?
Yes, until 31 January 2027 under standard support. From 1 February 2027 Azure Database for MySQL enrols 8.0 servers in paid Extended Support automatically, until 31 May 2029.
Is MySQL 8.0.46 end of life?
Yes. 8.0.46, released on 21 April 2026, is the final release of a series that ended on 30 April 2026, so Oracle will not ship an 8.0.47. Amazon's 8.0.46-RDS.20260624 and 8.0.46-RDS.20260908 builds carry 32 CVE fixes between them, for RDS Extended Support customers only.
What MySQL end of life support is available for 8.0?
Oracle's Extended Support for 8.0 ended on 30 April 2026. Amazon RDS sells paid Extended Support to 31 July 2029, Azure Database for MySQL does the same from 1 February 2027 to 31 May 2029, and OSSeva ships patched, signed 8.0 Community builds for servers you run yourself.
What is the difference between MySQL 8.0, 8.4 and 9.7?
8.0 reached end of life on 30 April 2026. 8.4 is an LTS series with Premier Support to April 2029 and Extended Support to April 2032; 9.7 is the next LTS, with Premier Support to April 2031 and Extended Support to April 2034. 8.0 upgrades to 8.4 and then to 9.7, because MySQL does not allow skipping an LTS series.
What should I upgrade MySQL 8.0 to?
8.4 LTS, then 9.7 LTS. MySQL does not support skipping an LTS series, so 8.0 cannot go straight to 9.7.
Can I get security patches for MySQL 8.0 after end of life?
Yes. OSSeva ships patched, signed MySQL 8.0 Community builds for self-managed servers. On Amazon RDS and Azure, the providers' own extended support programmes patch 8.0 instances on those services.
Get a quote
Still running MySQL 8.0?
Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.
Prefer to talk or read more first?