MySQL 8.0 end of life
MySQL 8.0 reached end of life on 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.
- 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.
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.
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. | Weeks, mostly authentication and replication tooling | Engineering time | The right answer for most estates. Plan the later move to 9.7 at the same time. |
| 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. | Days | 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.
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.
MySQL 8.0: common questions
When is MySQL 8.0 end of life?
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.
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.
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.