Adobe Commerce development
Storefront design
Performance & SEO
AI & agentic commerce
Release tracker
Magento 2.4.6 reached the end of standard support on August 11, 2026. For Adobe Commerce, it now sits in extended support, which still delivers quality and security patches for the core application until August 31, 2027. After that, a one-time security-only period with limited isolated security fixes runs until May 31, 2028, and then 2.4.6 receives nothing at all. If you run Adobe Commerce 2.4.6, the practical deadline to finish an upgrade or move is August 2027, not 2028. Adobe's lifecycle policy does not say that Magento Open Source gets extended or security-only support, so Open Source 2.4.6 stores should plan as if support ended in August 2026.
This post explains what each phase still covers, why PHP makes the timeline tighter than it looks, and how to choose between your options.
The 2.4.6 support timeline, phase by phase
All dates below come from Adobe's lifecycle policy. 2.4.6 became generally available on March 14, 2023.
| Phase | Dates | What you still get | What you no longer get |
|---|---|---|---|
| Standard support | March 14, 2023 to August 11, 2026 | Quality fixes, security patches and full Adobe Commerce support. | Ended. This phase is over. |
| Extended support | August 12, 2026 to August 31, 2027 | Quality and security patches for the core application. Adobe says this is at no extra cost for Adobe Commerce customers. | New features, and fixes for third-party dependencies that reach end of life (such as PHP 8.1 and 8.2). |
| Security-only period | September 1, 2027 to May 31, 2028 | Limited isolated security fixes only. Adobe describes this as migration time, and says it will not be extended. | Quality fixes of any kind, and broad security coverage. |
| Cloud enforcement | From June 1, 2028 | Nothing. Adobe Commerce on Cloud environments still on 2.4.6 face enforcement, which can include suspending traffic. | All support and patches. |
The latest 2.4.6 patch release as of May 12, 2026 is 2.4.6-p15. If you are on an earlier 2.4.6 patch, you are already missing fixes, and Adobe's isolated security patches are tested only against the latest -p version of each line.
Why PHP makes the deadline earlier than it looks
Adobe's system requirements list PHP 8.2 and 8.1 for 2.4.6-p15. That is the hidden problem.
- PHP 8.1 reached end of life on December 31, 2025.
- PHP 8.2 security support ends on December 31, 2026, according to php.net.
Adobe states that it does not fix third-party dependencies once they reach end of life, and its lifecycle page lists PHP 8.1 and 8.2 as PCI risks for older release lines. In practice, from January 2027 a 2.4.6 store runs on a PHP version that no longer receives security fixes from the PHP project, even while Adobe still patches the Magento code. Adobe also notes that PCI compliance is the merchant's responsibility to assess, so if you take card payments, talk to your qualified security assessor.
The same pattern applies to the database. 2.4.6-p15 no longer lists MySQL 8.0, which reached end of support on April 30, 2026. If you are still on MySQL 8.0, you are already outside Adobe's supported combinations.
Your options: upgrade, replatform or stay
Most 2.4.6 stores have three realistic paths. The matrix below compares them on what matters to the business.
| Factor | Upgrade to 2.4.9 | Replatform | Stay on 2.4.6 |
|---|---|---|---|
| Support after the move | Standard support to May 31, 2029 | Depends on the new platform | Extended support to August 31, 2027, then security-only to May 31, 2028 |
| Effort | Medium to high: three minor versions, PHP 8.2 to 8.5, new services | High: new platform, data migration, redirects, retraining | Low now, rising later as risk grows |
| Risk to SEO and sales | Low if URLs and templates stay the same | Medium to high without careful redirect and SEO work | Low short term; security and compliance risk grows after 2026 |
| Keeps your customizations | Yes, after compatibility fixes | No; must be rebuilt or replaced | Yes |
| Best for | Stores whose Magento setup still fits the business | Stores whose needs have changed a lot, or that want a different operating model | Only as a short bridge while an upgrade or move is under way |
Option 1: upgrade to 2.4.9
For most 2.4.6 stores, going straight to 2.4.9 is the most sensible move. You do the testing work once and land on a version supported until 2029. The jump is significant: PHP goes from 8.2 to 8.5, Elasticsearch is no longer supported, Redis is replaced by Valkey 9, and the database moves to MySQL 8.4 or MariaDB 12.3. Our overview of what's new in Magento 2.4.9 covers each of these changes and what to do about them.
Stopping at 2.4.7 or 2.4.8 rarely saves much. 2.4.7 leaves standard support in May 2027, so you would be planning the next upgrade almost immediately.
Option 2: replatform
Replatforming makes sense when your requirements have moved away from what Magento does well, for example if you have a small catalog, few integrations and no in-house development capacity. It is not automatically cheaper or faster than an upgrade, because it means rebuilding the storefront, migrating data, recreating integrations and protecting search rankings with redirects. Compare both routes on cost drivers, not headline prices. Our guide to Magento upgrade cost explains what makes an upgrade large or small.
Option 3: stay on 2.4.6 for now
Staying is a valid short-term choice if you have a firm plan. It is not a long-term strategy. If you stay, at minimum:
- Apply 2.4.6-p15 and every isolated security patch Adobe releases for it.
- Move off MySQL 8.0 if you have not already.
- Put the upgrade or migration project on the calendar with a finish date before August 31, 2027.
- Watch PHP 8.2's end of security support on December 31, 2026, and agree with your hosting provider how you will manage that risk.
A sensible timeline for 2.4.6 stores
- Now: run an upgrade audit. List extensions, custom modules, integrations and hosting versions, and check vendor support for 2.4.9.
- Next one to two months: decide on upgrade or replatform, and get a fixed scope based on the audit.
- By early 2027: have a staging environment running 2.4.9 with production-like data, and start testing.
- Spring 2027: go live, avoiding your peak trading periods.
- Before August 31, 2027: have the old 2.4.6 environment retired.
Keep an eye on new patch releases and dates for every line on our Magento release tracker.
FAQ
Is Magento 2.4.6 end of life?
For Adobe Commerce, not completely yet. Standard support ended on August 11, 2026. Extended support runs to August 31, 2027, and a security-only period runs to May 31, 2028. After that, 2.4.6 receives no patches. For Magento Open Source, Adobe's policy describes no extended support, so treat August 11, 2026 as the end.
Does extended support cost extra?
Adobe's lifecycle policy says extended support for 2.4.6 and 2.4.7 is offered at no additional cost for Adobe Commerce customers. The policy does not mention Magento Open Source, so Open Source users should not count on it and should check Adobe's security bulletins to see which lines receive patches.
Can I skip straight from 2.4.6 to 2.4.9?
Yes. Composer-based upgrades can move across several minor versions in one project. The work is in making extensions, custom code and services compatible with the target version, not in the number of versions skipped.
Planning your move off 2.4.6
The 2.4.6 clock is already running, and the PHP 8.2 date at the end of 2026 adds pressure. The earlier you audit, the more choice you have about timing. If you want an audit and a fixed-scope upgrade plan, Mistri's Magento upgrade services start there.
Sources
Adobe Commerce lifecycle policy (Adobe Experience League); System requirements (Adobe Experience League); Supported PHP versions (php.net).
