Adobe ended regular support for the 2.4.6 release line on 11 August 2026. If your store runs Magento Open Source or Adobe Commerce 2.4.6 or older, it is now outside the standard support window. The next line, 2.4.7, reaches the same point on 31 May 2027. That is closer than it sounds once peak trading and code freezes are taken out of the calendar.
Support dates for each 2.4.x line
| Release line | End of regular support |
|---|---|
| 2.4.5 | 12 August 2025 |
| 2.4.6 | 11 August 2026 |
| 2.4.7 | 31 May 2027 |
| 2.4.8 | 31 May 2028 |
| 2.4.9 | 31 May 2029 |
These are the dates on Adobe's released-versions page at the time of writing. Adobe has revised them before, so check its lifecycle policy when you plan.
What "extended support" covers, and who gets it
Adobe gives Adobe Commerce customers on 2.4.6 and 2.4.7 one year of extended support at no extra cost. For 2.4.6 that runs to 31 August 2027, and for 2.4.7 to 31 May 2028. Extended support includes quality and security patches for the core application, but Adobe does not list its full on-call support for that period. Adobe's policy describes extended support for Adobe Commerce customers only. It does not say that Magento Open Source stores get it, so if you run Open Source, plan as if 11 August 2026 was the end.
The PHP problem underneath
Adobe does not patch third-party dependencies such as PHP, MySQL or OpenSearch, even inside a support window. That matters for 2.4.6 in particular. Many 2.4.6 stores run PHP 8.1, which reached end of life on 31 December 2025, or PHP 8.2, which follows on 31 December 2026. Adobe itself flags the PCI compliance risk of running 2.4.4 to 2.4.6 on an unsupported PHP version. A store can be on a supported Magento patch and still be running an unpatched runtime underneath.
Which version to aim for
- If you are on 2.4.6 or older, go straight to 2.4.8 or later rather than stopping at 2.4.7, which only buys you until May 2027
- Check each third-party extension for a release that supports your target version before you commit to a date
- Plan the PHP, MySQL or MariaDB, OpenSearch and Redis or Valkey versions alongside Magento, since each 2.4.x line supports a specific set
- On Adobe Commerce Cloud, confirm your infrastructure versions with Adobe as part of the plan
Timing it around peak
Most retailers are now in a code freeze until after Christmas, and that is right: November is not the time to upgrade a commerce platform. Use the freeze to plan instead. Run an extension compatibility audit, set up a staging environment on the target version, and book the upgrade for January or February. That leaves time to test properly and still be finished well before 2.4.7's support ends in May.
If the upgrade keeps getting pushed back
Stores that have skipped several upgrades often find the gap has grown into a project of its own: abandoned extensions, heavily customised checkout code, and a theme that no longer fits the platform. If that describes your store, it is worth deciding whether to upgrade or replatform before spending the budget. London Design Works, our sister agency, can help plan a move with a Migration Blueprint.
On 2.4.6 or older?
We audit your extensions and infrastructure, prove the upgrade on staging and schedule go-live outside your trading peaks, for both Magento Open Source and Adobe Commerce.
See Magento support and maintenance →