OSSEVA FOR MYSQL
MySQL 8.0 is end of life. Your servers still need patches.
Oracle shipped the last MySQL 8.0 release, 8.0.46, in April 2026. OSSeva keeps 8.0 and 5.7 patched with signed builds of the Community Edition you already run, supports 8.4 LTS and 9.7 LTS beside them, and plans the upgrade at a pace your applications can take. No new database licence, no change of binaries on day one.
Last reviewed
Trusted globally by enterprises
Why now
MySQL 8.0 reached end of life on 30 April 2026
Oracle's Lifetime Support Policy ended Premier Support for 8.0 in April 2025 and Extended Support in April 2026. The 8.0 release notes say 8.0.46, released on 21 April 2026, marks the end of life, and point users to 8.4 LTS or an Innovation release. Vulnerabilities found since then are not fixed in any community 8.0 build. Amazon's Extended Support build 8.0.46-RDS.20260908 alone lists 31 CVE fixes.
Cloud providers now charge to stay on 8.0
Amazon RDS ended standard support for MySQL 8.0 on 31 July 2026 and bills RDS Extended Support from 1 August 2026, for up to three years. Azure Database for MySQL keeps 8.0 in standard support until 31 January 2027, then enrols servers in paid Extended Support automatically, billed per vCore hour. Self-managed MySQL on your own servers or Kubernetes has no equivalent unless you arrange one.
Enterprise Edition means an Oracle contract
MySQL Community Edition is GPL software and free to download. Enterprise Edition adds Enterprise Backup, the thread pool, transparent data encryption, audit, firewall, masking and 24x7 support, and only Oracle sells it. For a team working to reduce its Oracle footprint, buying Enterprise Edition to get support for Community servers adds a contract in the wrong direction.
One contract for MySQL and the rest of the stack
Most MySQL estates sit next to PostgreSQL, Redis or Valkey, Kafka and RabbitMQ, each with its own support arrangement and renewal date. OSSeva covers them under one contract, one renewal date and one escalation path, priced per cluster rather than per core, so consolidating support does not punish growth.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 5.7.x(Oracle EOL, OSSeva patched) | Extended | Clean |
| 8.0.x(Oracle EOL, OSSeva patched) | Extended | Clean |
| 8.4.x(LTS, Oracle Extended Support to Apr 2032) | Current | Clean |
| 9.7.x(LTS, recommended upgrade target) | Current | Clean |
| 9.0 to 9.6(Innovation lines; move to 9.7 LTS) | EOL | Clean |
| 26.7(Innovation release; supported on Assure and Operate, no patched builds) | Current | Clean |
What you get
Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.
OSSeva Patch
Backported security fixes for MySQL 5.7 and 8.0 Community builds.
- Patched builds for 5.7 and 8.0 following each quarterly Oracle Critical Patch Update
- Signed DEB and RPM packages, tarballs and container images
- Same major version, same data directory, same configuration
- CVE notifications with the fix status for your lines
- Upgrade planning to 8.4 or 9.7
- 24/7 managed operations
OSSeva Assure
Patches plus upgrade planning, configuration review and audit evidence.
- Everything in Patch
- Upgrade plan from 5.7 or 8.0 to 8.4, then 9.7, using MySQL Shell's upgrade checker
- Authentication review for mysql_native_password accounts before 8.4
- Replication, Group Replication and InnoDB Cluster topology review
- Compliance evidence: SBOMs and CVE remediation records
- 24/7 managed operations
OSSeva Operate
Day-to-day operations for your MySQL fleet, run by DBAs.
- Everything in Assure
- Critical CVEs (CVSS ≥ 9.0) patched within 48 hours and High within 7 days
- 24/7 replication lag, failover and backup monitoring
- 15-minute P1 incident response SLA
- Rolling upgrades executed replica by replica
- Quarterly capacity and performance reviews
All tiers priced per cluster/application — not per core. Contact for pricing →
How it installs
OSSeva artifacts arrive via your existing package infrastructure. Pull the patched version the same way you pull upstream today — just from the OSSeva registry.
SELECT VERSION();
-- mysql_native_password is not enabled by default from MySQL 8.4.0
SELECT user, host, plugin
FROM mysql.user
WHERE plugin = 'mysql_native_password';mysqlsh -- util check-for-server-upgrade root@db1:3306 \
--target-version=8.4.12 --output-format=JSON > db1-upgrade-check.jsoncurl -fsSL https://packages.osseva.io/gpg | sudo gpg --dearmor -o /usr/share/keyrings/osseva.gpg
echo "deb [signed-by=/usr/share/keyrings/osseva.gpg] https://packages.osseva.io/mysql $(lsb_release -cs) main" \
| sudo tee /etc/apt/sources.list.d/osseva-mysql.list
sudo apt update && sudo apt install mysql-server-8.0-ossevaMigrate from Oracle MySQL Enterprise support
Keep your binaries, change your support. OSSeva takes over support for the MySQL Community servers you run today with no migration, then ships its own patched builds on your schedule. If you use Enterprise-only components such as Enterprise Backup, TDE or Enterprise Firewall, we map each one to a community option or tell you plainly where Enterprise Edition remains the better fit.
Pricing model
OSSeva for MySQL is priced per cluster, not per core or per server. Book a discovery call for a quote.
Frequently asked questions
When did MySQL 8.0 reach end of life?
On 30 April 2026. Oracle's Lifetime Support Policy ended Extended Support for MySQL 8.0 in April 2026, and the final release on the line was 8.0.46, published on 21 April 2026. Oracle directs 8.0 users to 8.4 LTS or a current Innovation release.
What are the consequences of MySQL 8.0 end of life?
Oracle publishes no further 8.0 releases, so security fixes in later Critical Patch Updates reach 8.4, 9.7 and the Innovation track but not 8.0. Scanners keep flagging new MySQL CVEs against 8.0 servers, auditors treat an unsupported database as a finding under PCI DSS 6.3.3 and SOC 2 CC7.1, and managed services start charging for extended support. The servers keep running; what stops is the fix supply.
Which MySQL versions are still supported?
As of October 2026, Oracle supports MySQL 8.4 LTS, released April 2024 with Premier Support to April 2029, and 9.7 LTS, released April 2026 with Premier Support to April 2031. The current Innovation release is 26.7, supported until the next Innovation release. MySQL 8.0 and 5.7 are end of life, and the 9.0 to 9.6 Innovation lines ended as each successor shipped.
What is the MySQL support lifecycle?
MySQL runs two tracks. LTS series follow Oracle's Lifetime Support Policy: five years of Premier Support and three years of Extended Support, with no feature removals inside the series. Innovation releases add features and behaviour changes and are supported only until the next Innovation release. After 9.7, versions follow a calendar scheme, so 26.7 is the July 2026 release.
Is MySQL Enterprise Edition free?
No. MySQL Community Edition is free to download under the GPL. Enterprise Edition is a commercial subscription that only Oracle sells, bought through the Oracle Store, Oracle sales or channel partners. It adds components such as Enterprise Backup, the thread pool, TDE, audit, firewall and masking, together with 24x7 Oracle support.
Does Amazon RDS or Azure still support MySQL 8.0?
Both offer paid extended support. Amazon RDS ended standard support for 8.0 on 31 July 2026 and runs RDS Extended Support from 1 August 2026 to 31 July 2029. Azure Database for MySQL keeps 8.0 in standard support until 31 January 2027, then enrols servers automatically in Extended Support to 31 May 2029. Neither covers MySQL you run yourself.
Can OSSeva support the MySQL servers we run today without a migration?
Yes. OSSeva takes over support for the Community Edition binaries and data you already have. Patched builds stay on the same major version, so moving to one is the same as a minor update: replace the packages and restart on the same data directory, replicas first in a replicated topology.
Should we upgrade from 8.0 to 8.4 or straight to 9.7?
MySQL does not allow skipping an LTS series, so 8.0 moves to 8.4 first and 9.7 after that. Servers on 5.7 go to 8.0, then 8.4. The work in the 8.4 step is usually authentication, because mysql_native_password is no longer enabled by default, and replication scripts that still use the removed CHANGE MASTER TO and START SLAVE statements.
When is MySQL Enterprise Edition the better fit?
When you depend on Enterprise-only components and want them supported by the vendor that writes them, for example Enterprise Firewall, Enterprise TDE with a key vault, or MySQL HeatWave. In that case Oracle is the natural supplier. OSSeva fits estates that run Community Edition and want support without an Oracle contract.
Does OSSeva also support MariaDB?
Yes. Many estates run MySQL and MariaDB side by side, and both can sit under the same OSSeva contract. The MariaDB page covers its LTS lines and end-of-life dates.
Ready to get MySQL patched and supported?
Start with a 45-minute discovery call. We confirm your version coverage, scope the engagement, and have you onboarded within your first quarter.