Magento 2.4.9: What's New and What It Means for Your Store

Magento 2.4.9 (Adobe Commerce and Magento Open Source) became generally available on May 12, 2026. It is mainly a platform release: it runs on PHP 8.5, uses Valkey 9 for cache and sessions, requires MySQL 8.4 or MariaDB 12.3, and replaces several old framework parts such as Laminas MVC and Zend_Cache. Standard support for 2.4.9 runs until May 31, 2029, which makes it the safest target for anyone planning an upgrade in 2026 or 2027.

This guide covers what changed, what each change means for your store, and what you or your developers need to do about it.

Magento 2.4.9 at a glance

• Release date: May 12, 2026 (general availability).
• End of standard support: May 31, 2029, three years from release under Adobe's lifecycle policy.
• Editions: the same release line covers Adobe Commerce (on-premises and on Cloud infrastructure) and Magento Open Source.
• Headline requirement: PHP 8.5. Adobe's release notes say PHP 8.4 is allowed for upgrade purposes only and is not recommended for production.
• Next version: 2.4.10-alpha1 was released on October 13, 2026. Alpha builds are for testing extensions, not for live stores.

If you run an older line, the date that matters most is your own end of support. 2.4.6 left standard support on August 11, 2026, and 2.4.7 leaves it on May 31, 2027. Our guide to Magento 2.4.7 end of support walks through a plan that works back from that date.

Platform changes in 2.4.9 vs 2.4.8

The table compares the on-premises requirements for 2.4.9 with the latest 2.4.8 patch (2.4.8-p5), as listed on Adobe's system requirements page. Adobe supports only the combinations it lists, so treat each row as a hard requirement, not a suggestion.

The practical takeaway: if you are already on 2.4.8-p5 with MySQL 8.4 or a current MariaDB, OpenSearch 3 and Valkey 8.1, the infrastructure jump to 2.4.9 is small. The PHP 8.5 move and the framework changes below are where most of the work sits. If you are coming from 2.4.6 or 2.4.7, almost every row changes at once.

Framework and code changes developers should know

Beyond the services table, 2.4.9 removes or replaces several libraries that have been in Magento for years. These matter most for custom modules and older extensions.

Laminas MVC replaced by a native implementation

Adobe's release notes say Laminas MVC has been replaced with a native MVC implementation. Code that relies directly on Laminas MVC classes, rather than on Magento's own interfaces, is the most likely to break. Well-built modules that use Magento's service contracts, plugins and observers should be less affected.

Zend_Cache replaced by Symfony Cache

The cache layer now uses the Symfony Cache component. Custom cache frontends, backends or code that calls Zend_Cache classes directly needs review. Standard cache types and the Admin cache management screen work as before.

TinyMCE replaced by HugeRTE

The Admin WYSIWYG editor has moved to HugeRTE. Extensions that add TinyMCE plugins or customize the editor toolbar need checking, and content editors should test their usual workflows in staging.

Other dependency updates

• Symfony components updated to the 7.4 LTS line.
• PHPUnit upgraded to 12.x, which affects custom unit and integration test suites.
• The third-party OAuth library was replaced by native PHP OAuth functions.
• Several JavaScript libraries were updated, including jQuery UI 1.14.1, jQuery Validate 1.21.0 and Chart.js 4.5.0. Custom frontend code that depends on old jQuery UI behavior needs a check.

Because 2.4.9 requires PHP 8.5, the PHP move deserves its own plan. Our guide to moving Magento to PHP 8.5 lists the typical failure types and how to find them before they reach production.

New features merchants will notice

2.4.9 is not a big feature release, but several changes are visible to store teams.

Security

• CAPTCHA is enforced for customer account creation through REST and GraphQL, which closes a common route for fake account sign-ups.
• reCAPTCHA is enforced on more GraphQL mutations, including contact forms, customer updates and coupon application.
• Admins need only one enabled two-factor authentication provider to sign in, and the minimum Admin password length is configurable.

Admin and merchandising

• The Catalog Price Rules grid has an Actions menu for bulk activate, deactivate and delete.
• Cart merge behavior (what happens when a guest with a cart logs in) is configurable under Sales > Checkout.
• Inventory sources can now be deleted.
• Adobe Commerce staging has an improved mobile preview.

APIs

• The clearCart GraphQL mutation is now available in Magento Open Source, not only Adobe Commerce.
• New mutations include clearWishlist and exchangeExternalCustomerToken for integration-based authentication.
• Malformed REST requests now return HTTP 400 instead of 500, and bulk API endpoints expect array payloads with consecutive keys starting at 0. Integrations that send loosely formed payloads should be tested.
• A REST product update at store-view scope no longer pulls in global image and video changes when media_gallery_entries is omitted or null. If a PIM or ERP sync relies on the old behavior, test it.

Payments and shipping

• The bundled Braintree module adds promo codes in Apple Pay and Google Pay express sheets, Apple Pay on Chrome and Firefox, and new local methods such as BLIK (Poland) and Pay Upon Invoice (Germany).
• USPS integration moved to USPS's REST APIs, and DHL added MyDHL REST support. The legacy APIs remain selectable, but carriers are retiring old endpoints, so switching early is sensible.

Who should upgrade to 2.4.9, and when

The answer depends on where you are today.

• On 2.4.8: you are supported until May 31, 2028, so there is no emergency. Plan 2.4.9 as a scheduled project once your key extensions declare 2.4.9 and PHP 8.5 support. Moving earlier gives you an extra year of standard support.
• On 2.4.7: standard support ends May 31, 2027. Going straight to 2.4.9 usually makes more sense than stopping at 2.4.8, since you do the testing work once and get support to 2029.
• On 2.4.6 or older: standard support has already ended. 2.4.6 receives quality and security patches for the core application during extended support, which runs to August 31, 2027. 2.4.4 and 2.4.5 are in a security-only period that ends May 31, 2027. These stores should start upgrade planning now.
• On Adobe Commerce on Cloud: Adobe's lifecycle policy sets enforcement dates for unsupported versions, starting June 1, 2027 for 2.4.4 and 2.4.5. Check your line's enforcement date on the lifecycle page.

Release dates, patch levels and support windows for every line are kept up to date on our Magento release tracker.

How to prepare for the 2.4.9 upgrade

1. Inventory your extensions and custom modules. List every third-party module with its version and check whether the vendor supports 2.4.9 and PHP 8.5. Mark any module that is no longer maintained.
2. Check your hosting stack. Confirm your host can provide PHP 8.5, Valkey 9, OpenSearch 3 and MySQL 8.4 or MariaDB 12.3. Managed hosts often roll out new service versions on their own schedule.
3. Build a staging copy with production-like data. Upgrade there first, with the same services and versions you will run in production.
4. Scan custom code. Run static analysis for PHP 8.5 deprecations and search for direct use of Laminas MVC, Zend_Cache and TinyMCE APIs. Adobe Commerce customers can also use Adobe's Upgrade Compatibility Tool.
5. Test the money paths. Checkout, payments, tax, shipping rates, customer login, search and every integration (ERP, PIM, marketplace feeds) need hands-on testing, not just a smoke test.
6. Plan the cutover. Agree a deployment window, a rollback plan and who checks what after go-live.

For the full step-by-step list with an owner for each task, use our Magento upgrade checklist.

FAQ

Is Magento 2.4.9 stable enough for production?

2.4.9 is a general availability release, which is Adobe's production-ready release type. The practical question is whether your extensions support it. Wait for your critical vendors to confirm compatibility, then test in staging.

Can I run 2.4.9 on PHP 8.4?

Adobe's system requirements list PHP 8.5 for 2.4.9. The release notes allow PHP 8.4 for upgrade purposes only, not for production, so plan to run PHP 8.5 in production.

Do I have to switch from Redis to Valkey?

For 2.4.9, Adobe lists Valkey 9 and does not list Redis. Valkey is a Redis-compatible fork, so Magento's configuration for it is very similar, but you should still test sessions and cache behavior after the switch.

Should I skip 2.4.9 and wait for 2.4.10?

Only 2.4.10-alpha1 exists as of November 2026, and Adobe has not published its general availability date on the lifecycle page. If your current line is near or past end of support, waiting for an unreleased version adds risk without a clear benefit.

Getting help with your 2.4.9 upgrade

Most 2.4.9 upgrades succeed or fail on preparation: an honest extension inventory, a staging environment that matches production, and real testing of checkout and integrations. If you would like a team to audit your store and run the upgrade end to end, Mistri's Magento upgrade services start with exactly that audit.

Sources

Adobe Commerce 2.4.9 release notes (Adobe Experience League); System requirements (Adobe Experience League); Adobe Commerce lifecycle policy (Adobe Experience League); Supported PHP versions (php.net).