Magento 2.4.6 end of support: upgrade or replatform before PHP 8.2 ends

Magento 2.4.6 end of support is no longer a future event. Adobe Commerce 2.4.6 left standard support on 11 August 2026, and its extended support runs out on 31 August 2027. The date that should move your upgrade up the backlog is sooner: Adobe's own lifecycle page warns that stores running 2.4.6 on PHP 8.2 put PCI compliance at risk from the end of 2026. For a merchant taking card payments, that is 31 December.

This guide sets out the dates from Adobe's published lifecycle policy, what they mean for a store today, and how to decide between upgrading and moving to another platform.

Magento 2.4.6 end of support and the other lifecycle dates

Adobe's lifecycle policy, last updated on 19 August 2026, lists these dates:

Version	Released	Standard support ends	Extended support ends
2.4.9	12 May 2026	31 May 2029	—
2.4.8	8 April 2025	31 May 2028	—
2.4.7	9 April 2024	31 May 2027	31 May 2028
2.4.6	14 March 2023	11 August 2026	31 August 2027
2.4.5	9 August 2022	12 August 2025	11 August 2026
2.4.4	12 April 2022	12 April 2025	14 April 2026

Adobe added a year of extended support at no extra cost for 2.4.6 and 2.4.7, covering quality and security patches for the core application. For 2.4.4, 2.4.5 and 2.4.6 there is also a one-time, security-only transitional period — isolated security fixes, no quality fixes — which Adobe says will not be extended again.

For Commerce on Cloud, Adobe describes an enforced version-upgrade policy starting 1 June 2027. Check the Security and Compliance Notice linked from the lifecycle page for the exact actions that apply to your environment.

Is Magento 2.4.6 still supported?

Partly. It receives extended-support patches until 31 August 2027, so the core application still gets security fixes. But extended support covers the core application only. Adobe is explicit that it does not provide fixes for third-party dependencies — PHP, MariaDB or MySQL, OpenSearch, Redis, Valkey, RabbitMQ — that reach end of life while you are in extended support.

That is where the real exposure sits. Adobe's own dependency table flags two PHP dates:

• PHP 8.1, which reached end of life on 31 December 2025, is used by some 2.4.4, 2.4.5 and 2.4.6 installations. Adobe marks those as a PCI compliance risk now.
• PHP 8.2 reaches end of life on 31 December 2026, according to the PHP project's supported-versions page. For 2.4.6 on PHP 8.2, Adobe says PCI compliance is at risk from the end of 2026 and advises planning an upgrade or migration before then.

PCI compliance is the merchant's responsibility to assess, as Adobe notes. But an assessor looking at an unsupported language runtime on a payment-handling server will ask the question, and "the application is still patched" is not a complete answer.

What happens if you do not upgrade Adobe Commerce?

Nothing breaks on the day. The store keeps running. What changes is the risk profile: new vulnerabilities in PHP, the search engine or the cache stop being fixed; extensions start dropping support for old versions; and payment compliance becomes harder to evidence. Unpatched e-commerce platforms are a well-worn target, and the work to prioritise those exposures is the same as for any other stack — our guide to vulnerability prioritization applies directly.

The practical consequence is that the upgrade cost does not go away by waiting. It grows, because the gap to a supported version widens and the extensions you depend on move on.

Upgrade to 2.4.8 or 2.4.9, or replatform?

This is the real decision, and it depends on what your store has become.

When an upgrade is the right call

• Your customisation is modest: a theme, a handful of well-maintained extensions, standard checkout.
• Magento's catalogue, pricing and B2B features are genuinely used, not just installed.
• Your team or agency knows the codebase and has upgraded it before.

In that case, go straight to a version with a long runway. 2.4.8 is supported until May 2028 and 2.4.9 until May 2029. As Codilar notes in its 2.4.5 end-of-support guide, 2.4.8 brings changes across infrastructure dependencies, security architecture and APIs, so treat it as a project with a test plan, not a routine patch.

When replatforming deserves a serious look

• Every upgrade becomes a multi-month project because of custom modules and patched core files.
• Most of the platform's features are unused, and you are paying to maintain them.
• Your differentiation is in the front end, mobile app or fulfilment logic, not in Magento itself.
• You are on Commerce Cloud and the licence is a large share of your e-commerce budget.

The options then range from a hosted platform such as Shopify Plus for standard retail, to a headless architecture that keeps a commerce engine behind your own storefront and apps, to a custom build where the ordering flow is the product. We built a quick-commerce app on that last model because its delivery logic did not fit a packaged catalogue-and-cart system. Our broader framework for custom versus off-the-shelf software applies.

How long does a Magento 2.4.8 upgrade take?

It depends almost entirely on customisation, which is why honest estimates start with an audit. The drivers are the number of custom modules, how many third-party extensions have compatible releases, whether core files were patched directly, and how good the automated test coverage is. A lightly customised store may take a few weeks including testing; a heavily modified one can take months. Get the audit before you get the quote.

A plan for the next 100 days

1. Confirm your versions. Adobe Commerce version, PHP version, database and search engine versions, and whether you are on Cloud or self-hosted.
2. Audit extensions. List every third-party and custom module, and check which have releases for 2.4.8 or 2.4.9.
3. Talk to your PCI assessor. Ask how they will treat PHP 8.2 after 31 December.
4. Price both paths. Upgrade effort against the cost of replatforming, over three years rather than one.
5. Book the work. A December upgrade in peak trading season is the worst of both worlds; schedule it before or after.

Legacy e-commerce is a modernisation problem like any other, and the principles in our guide to modernising without breaking the business hold. If you want both paths costed properly, our e-commerce solutions team can audit your store and lay out the upgrade and the alternatives side by side.