Magento 2.4.6 end of support: upgrades and security patching
Magento 2.4.6 standard support ended Aug 11, 2026; extended support ends Aug 31, 2027. Senior Magento 2 developer in San Diego for Adobe Commerce upgrades, security patches, or a replatform to Shopify.
Adobe Commerce 2.4.x support windows
Standard support for Adobe Commerce 2.4.6 ended on August 11, 2026. It is now in extended support, which Adobe provides at no additional cost, until August 31, 2027. 2.4.5 and 2.4.4 are already past extended support and receive isolated security fixes only.
If your store runs 2.4.6 or older, you have a decision to make within the next year: upgrade to a supported release, or replatform. I'm a senior Magento 2 developer in San Diego and I've done both, so this page covers both honestly.
The support dates that matter
| Version | Standard support ended / ends | Extended support ends | Security-only fixes until |
|---|---|---|---|
| 2.4.4 | Apr 12, 2025 | Apr 14, 2026 | May 31, 2027 |
| 2.4.5 | Aug 12, 2025 | Aug 11, 2026 | May 31, 2027 |
| 2.4.6 | Aug 11, 2026 | Aug 31, 2027 | May 31, 2028 |
| 2.4.7 | May 31, 2027 | May 31, 2028 | |
| 2.4.8 | May 31, 2028 | ||
| 2.4.9 | May 31, 2029 |
2.4.9 was released on May 12, 2026. Extended support for Adobe Commerce is complimentary: quality and security patches at no additional cost. The one-time security-only period that follows for 2.4.4, 2.4.5 and 2.4.6 delivers isolated security fixes and no quality fixes. Magento Open Source follows the standard support window, so Open Source 2.4.6 and older are already outside it.
Source: Adobe Commerce lifecycle policy. Last checked Sep 25, 2026.
Upgrade or replatform?
Upgrade when Magento still fits the business: complex catalogs, B2B, heavy customization you rely on, or several websites on one install. An upgrade to 2.4.8 or 2.4.9 buys the longest runway: standard support until May 31, 2028 or May 31, 2029.
Replatform when the store has outgrown the cost of running Magento, or never needed its flexibility in the first place, and a hosted platform would let your team work without a developer for every change. For many merchants that means Magento to Shopify.
If you're not sure, a migration discovery audit answers the question with your own code and data rather than a sales pitch.
What an upgrade actually involves
A Magento minor-version upgrade is rarely a single Composer command. The work I plan for:
- Platform requirements. Newer releases need newer PHP, database, search engine, Redis, Varnish and Composer versions. Hosting changes often come first. I check against Adobe's system requirements for the exact target release.
- Third-party extensions. Every extension needs a compatible version, a replacement, or removal. This is usually where the time goes.
- Custom modules and themes. Deprecated APIs, changed dependencies and template overrides that no longer match core are found and fixed.
- Security patches. Outstanding patches and hotfixes are reconciled so nothing is lost or applied twice.
- Testing. Checkout, payments, integrations, indexing and cron are tested on staging with production-like data before anything goes live.
- Deployment. A planned release with a rollback path, whether on your own infrastructure, AWS or Magento Cloud.
Why me
At Event Network I managed upgrades, security patches and Adobe Commerce features across 18 Magento 2 storefronts on a shared codebase, where one upgrade had to work for every store. I've worked on Magento since 2012, across Magento 1 and 2, Open Source and Adobe Commerce, and I've led migrations off Magento when that was the better answer. You'll get a recommendation, not a default.
Questions
Is extended support something we have to buy? No. For Adobe Commerce, Adobe provides extended support at no additional cost. For 2.4.6 it runs until August 31, 2027.
What happens after August 31, 2027? 2.4.6 moves into a one-time security-only period until May 31, 2028: isolated security fixes, no quality fixes. After that there are no patches at all.
We're on Magento Open Source. Does this apply to us? Open Source follows the standard support window, so Open Source 2.4.6 and older are already outside it. The upgrade decision is the same, with less time.
Should we jump straight to 2.4.9? Often yes, since it has the longest support window (to May 31, 2029), but it depends on whether your extensions and hosting support it today. That's the first thing I check.
Get a straight answer on your upgrade
Tell me your current version, edition (Adobe Commerce or Open Source), hosting, and roughly how many third-party extensions you run.
Available now · full-time or contract
Need a senior Magento lead? Let’s talk.