Magento Open Source / Adobe Commerce 2.4.9 landed on 12 May 2026. Read past the 581-fix headline and a pattern shows up fast: this is a platform release, not a feature release. The consequential decisions in 2.4.9 are all about the foundation your store runs on, not what your customers see.
What kind of release this is
Adobe ships two flavours of feature release. Some are merchant-facing - new checkout, new admin tooling. Others are housekeeping: drop old dependencies, raise the minimum stack, clear technical debt so the platform can keep moving. 2.4.9 is firmly the second kind. The genuinely important changes are all requirements - a newer PHP, Symfony 7.4 LTS, and a hard jump in the supported database. The customer-facing additions are real but modest.
That framing changes the question. You don't upgrade to 2.4.9 for a feature - you upgrade because staying current on a modernizing platform is cheaper than falling behind it.
The database is the real gatekeeper
2.4.9 requires MySQL 8.4 LTS or MariaDB 11.4 LTS and drops MySQL 8.0 and MariaDB 10.6 entirely. For a lot of stores, that is the upgrade. And here's the part worth thinking about: the hard part isn't upgrading Magento itself, it's the database and hosting underneath it. On budget or managed hosting - where the database version often isn't yours to choose - this can quietly turn into a hosting migration, not a config change. That's the real cost of a modernization release, and it's the line item people forget to budget.
PHP 8.5 (alongside 8.3 and 8.4), Symfony 7.4 LTS and first-class Valkey caching round out the platform move. None of it forces your hand the way the database does, but together they're Adobe signalling that the old stack's days are numbered.
The features, honestly
If you take cards through Braintree, two additions are worth real attention. Google Pay Vault lets customers save and reuse a Google Pay card. Quieter but arguably more valuable is the Real-Time Account Updater: vaulted Visa, Mastercard and Discover cards refresh automatically when they're reissued - which directly attacks the declined-renewal revenue leak that bleeds subscription and repeat-purchase stores. (ELO support lands too, relevant if you sell into Brazil.) On the API side, the clearCart, clearWishlist and exchangeExternalCustomerToken GraphQL mutations close real gaps for headless builds.
But be honest about the weight of all this: it's incremental. If you were hoping 2.4.9 would hand you a transformative new store capability, it doesn't. It hands you a more current foundation, and the 581 core bug fixes - the unglamorous, real argument for being on a current line: long-standing issues across APIs, cart, checkout, taxes and catalog that, individually, never make a headline.
Security is the one piece that isn't optional: the latest patch, APSB26-49 (12 May 2026), covers the supported older lines against flaws rated up to CVSS 8.7 (stored XSS, path traversal). Patch that now, on its own - it has nothing to do with the feature upgrade and shouldn't wait on it.
Should you be first in line?
Here's the part the changelogs never discuss: timing. The initial release of a big platform-shift version is, almost by definition, the least battle-tested. Extension vendors haven't all certified compatibility, and the early edge cases haven't surfaced yet. There's an old instinct in software - never ship on someone else's .0 - and it applies here: with Magento, the patch releases (2.4.9-p1, p2 and on) are exactly where the teething problems of an initial release get shaken out.
So for most stores the pragmatic read is: plan the move now, deploy it a little later. Plan now because the prerequisites - database, PHP, extension compatibility - take real calendar time to line up. Deploy after the first patch release or two, once the ecosystem has caught up - unless you have a concrete reason to be early (a feature you genuinely need, or a fix you can't get on your current line).
The counter-pressure is real, though. This is a modernization release, so the longer you sit on an old line, the larger the eventual jump - and the database requirement only gets more painful the further behind you fall. The flip side: 2.4.9 is built deliberately on LTS components (Symfony 7.4 LTS, MySQL 8.4 LTS, MariaDB 11.4 LTS) with regular support to May 2029. Adobe clearly means it as a long-lived, stable base. That makes it a good version to aim for - worth settling on, just not necessarily on day one.
Version history
| Version | Released | PHP | The story |
|---|---|---|---|
| 2.4.9 | May 2026 | 8.3 / 8.4 / 8.5 | Platform reset: MySQL 8.4 / MariaDB 11.4 required, Symfony 7.4, Valkey, 581 fixes |
| 2.4.8 | 2025 | 8.3 / 8.4 | feature release |
| 2.4.7 | 2024 | 8.2 / 8.3 | feature release |
Verified against Adobe's official 2.4.9 release notes.
Planning a move to 2.4.9, or stuck on an older line because of the database jump? We do Magento upgrades and audits - including the hosting and extension-compatibility parts that actually break. Talk to us.
Frequently Asked Questions
What is the latest version of Magento in 2026?
Magento Open Source / Adobe Commerce 2.4.9 is the current release as of May 2026. It requires MySQL 8.4 LTS or MariaDB 11.4 LTS and supports PHP 8.3, 8.4, and 8.5. It ships with Symfony 7.4 LTS, Valkey caching, and 581 core bug fixes. Adobe's official 2.4.9 release notes detail every change.
Should I upgrade to Magento 2.4.9 right away?
For most stores, the pragmatic approach is to plan now and upgrade after the first patch release (2.4.9-p1). Initial releases of major platform versions have the highest concentration of edge-case issues; extension vendors may not have certified compatibility yet. The prerequisites - database version, PHP version, extension audits - take real calendar time to line up, so start planning immediately even if deployment waits a few months.
What database does Magento 2.4.9 require?
Magento 2.4.9 requires MySQL 8.4 LTS or MariaDB 11.4 LTS. Support for MySQL 8.0 and MariaDB 10.6 is dropped. On shared or managed hosting where the database version is not under your control, this requirement can turn an application upgrade into a hosting migration - which is the line item most upgrade budgets miss.
What PHP versions does Magento 2.4.9 support?
Magento 2.4.9 supports PHP 8.3, 8.4, and 8.5. PHP 8.2 is no longer supported. PHP 8.5 support is new in this release. All three supported versions are current, maintained PHP releases. If your server is on PHP 8.2 or lower, a PHP upgrade is required before or during the Magento upgrade.
How important is patching Magento separately from the feature upgrade?
Security patches are separate from feature upgrades and should not wait on the full upgrade timeline. APSB26-49, released 12 May 2026, covers vulnerabilities rated up to CVSS 8.7 - including stored XSS and path traversal - across the supported Magento lines. Apply the security patch to your current version immediately; schedule the feature upgrade separately on its own timeline.