MySQL 8.0 stopped receiving support on 30 April 2026, and Magento 2.4.9 no longer supports it either. Here's what database you should actually be planning to move to.

MySQL 8.0 reached end of life on 30 April 2026: no more security patches from Oracle, full stop. Less than two weeks later, Magento 2.4.9 went generally available with MySQL 8.0 support removed entirely. The two events landing almost on top of each other isn't a coincidence so much as a reminder of how long these decisions get planned in advance, and it means anyone upgrading to 2.4.9 needs to treat the database migration as part of the same project, not an afterthought bolted on at the end.
This is a different kind of risk than an application-level deprecation. A database holds every order, every customer record, every piece of your business that actually matters, and it's usually the component least touched day-to-day, which is exactly why EOL databases tend to linger far longer than they should. Once Oracle stops patching MySQL 8.0, any newly discovered vulnerability sits there unfixed indefinitely. Managed-database providers (AWS RDS, Google Cloud SQL, Azure Database for MySQL) also tend to force the issue eventually on their own schedule, deprecating EOL engine versions and requiring an upgrade whether or not you've planned for it. So even if you're not managing the database yourself, this isn't necessarily something you can simply leave alone.
Adobe's officially tested combination for 2.4.9 is MySQL 8.4 LTS, with MariaDB 12.3 supported as an alternative for merchants who prefer it (MariaDB 11.8 is also listed as an option on Adobe Commerce Cloud specifically). MySQL 8.0 and MariaDB 10.6 are both explicitly dropped in this release, alongside OpenSearch 2.x in favour of OpenSearch 3.
Treat the exact version numbers above as a starting point rather than the final word: Adobe's official system requirements documentation lists the precise supported combinations, and it's worth checking that table directly against your specific hosting setup before you commit to a migration plan, since these details do get refined between minor releases.
A few things worth deciding before you touch production:
Can I stay on MySQL 8.0 if I don't upgrade to Magento 2.4.9 yet? Technically yes, your current Magento version will keep running against it, but you're running an unpatched database with no further security fixes coming from Oracle, which is a growing risk the longer it continues, independent of what Magento version you're on.
What's the difference between MySQL 8.4 LTS and the Innovation release track? LTS (Long Term Support) releases prioritise stability and get an extended support window, which is what you want for a production e-commerce database. Innovation releases ship new features faster but on a much shorter support cycle: not the right choice for something running your store.
If you'd like the database side of a Magento upgrade planned alongside the application side rather than treated as a separate problem, that's exactly the kind of infrastructure planning our upgrade team handles as part of a Magento 2.4.9 migration.
Sources: i95dev's Magento 2.4.9 release guide, mgt-commerce's Magento 2.4.9 breakdown.
Last updated 16 May 2026.