Magento 2.4.6 is out of support: your options before August 2027

On 11 August 2026, Magento 2.4.6 reached the end of its three-year regular support period. On the same day, extended support for 2.4.5 ended. If your store runs either release, you are on borrowed time, and the exact amount depends on whether you run Adobe Commerce, Adobe Commerce on Cloud or Magento Open Source.

The most important date for Adobe Commerce merchants on 2.4.6 is now 31 August 2027, when extended support ends. After that, only limited security fixes remain until 31 May 2028. That sounds like a long time, but a major upgrade with extension changes, a PHP jump and full regression testing commonly needs several months, and peak trading season sits in the middle of the window.

This guide lays out the official dates, what “extended support” actually covers, the Cloud enforcement rules, and the options in front of you.

The official support dates

These dates come from Adobe’s released versions page and software lifecycle policy.

Note the 2.4.7 line: regular support runs until 31 May 2027, not into the following year. A move from 2.4.6 to 2.4.7 today buys only months of regular support.

What extended support covers, and what it does not

Adobe describes extended support as quality and security patches for the core application for up to one year beyond regular support, at no extra cost. After that, 2.4.4, 2.4.5 and 2.4.6 enter a one-time transitional window with limited isolated security fixes only and no quality fixes. Adobe says those windows will not be extended beyond the published dates.

Three caveats matter in practice:

• Third-party technology is excluded. Adobe does not support third-party technologies that have reached end of support. If your PHP, MySQL or MariaDB version is past its end of life, keeping it PCI compliant is your responsibility.
• The policy is written for Adobe Commerce. Adobe’s lifecycle documentation discusses extended support for Adobe Commerce. Magento Open Source merchants should check whether isolated patches are actually published for their release line each month rather than assume coverage.
• Extensions are on their own schedule. Extension vendors often stop testing against older lines well before Adobe does.

Security patches remain essential. In September 2026, Adobe shipped an emergency hotfix for CVE-2026-75650 (StyleSmuggler), an actively exploited unauthenticated remote code execution flaw rated CVSS 10.0 that affects 2.4.4 through 2.4.9. Stores on older lines depend on Adobe continuing to release such fixes for them.

Adobe Commerce on Cloud: enforcement deadlines

If you run Adobe Commerce on Cloud (PaaS), Adobe’s security enforcement policy sets hard deadlines. If they are missed, Adobe states it may suspend traffic to the affected infrastructure, taking the storefront offline, and with continued non-compliance may terminate the cloud services and start decommissioning, which permanently deletes data.

Two clarifications. First, the 1 June 2027 version-upgrade deadline applies to 2.4.4 and 2.4.5. For 2.4.6 on Cloud, the version-upgrade deadline is 1 June 2028. Second, a 2.4.6 store still has third-party software deadlines that fall on 30 October 2026 or 31 May 2027. Those are close.

Adobe states this policy does not apply to Adobe Commerce as a Cloud Service (SaaS) or to on-premises deployments.

Your options

Option 1: Upgrade to 2.4.9

2.4.9 gives the longest runway, with regular support until 31 May 2029. It is also the largest technical jump from 2.4.6: PHP 8.5 (PHP 8.2 and 8.3 are no longer supported), Symfony 7.4 LTS, a native MVC layer replacing Laminas MVC, Symfony Cache replacing Zend_Cache, and HugeRTE in place of TinyMCE.

Choose this when you want one upgrade that lasts and your extension stack has 2.4.9-compatible versions.

Option 2: Upgrade to 2.4.8

2.4.8 is supported until 31 May 2028. It is a smaller step for some stores, but it still involves a significant PHP and dependency upgrade from 2.4.6. You would face another upgrade decision in about 18 months. Choose this only if a critical extension or integration is not yet ready for 2.4.9.

Option 3: Move to Mage-OS

Mage-OS is a community-driven distribution of Magento Open Source. Mage-OS 3.0 is built on Magento Open Source 2.4.9, and Mage-OS ships its own releases, including 3.5.0 on 8 September 2026, which ported the StyleSmuggler fix. Mage-OS provides fixes for its latest release branch only, so this path still means staying current.

Mage-OS is relevant for Magento Open Source merchants. It does not replace Adobe Commerce licensed features or Adobe’s support contract.

Option 4: Replatform

Some businesses use an end-of-support moment to reassess the platform. A replatform is a full project: data migration, URL and SEO preservation, integrations, retraining and a new extension ecosystem. It rarely fits inside a few months. If you are leaning this way, you still need a supported, patched Magento store while the new one is built.

A practical plan for the next six months

1. Confirm your exact version and edition.

   bin/magento --version
   composer show | grep -E "magento/product-(community|enterprise)-edition"

2. Check you are fully patched today, including the APSB26-146 hotfix and the APSB26-138 September update.
3. Audit your stack: PHP, database, search, cache and message queue versions against the 2.4.9 system requirements.
4. Inventory extensions and check each vendor’s compatibility statement.

   bin/magento module:status --enabled | grep -v "^Magento_"

5. Pick a target (2.4.9, 2.4.8, Mage-OS or replatform) and set a go-live date well before your nearest deadline.
6. Build a staging environment on the target stack and run a trial upgrade with production data.
7. Schedule the cutover outside peak season, with a rollback plan.

Frequently asked questions

Will my 2.4.6 store stop working?

On-premises and self-hosted Magento keeps running. The risk is unpatched vulnerabilities, PCI compliance and extension compatibility. Adobe Commerce on Cloud is different: missing Adobe’s enforcement deadlines can lead to traffic suspension.

Is the Cloud traffic suspension deadline 1 June 2027 for 2.4.6?

No. Per Adobe’s security enforcement policy, 1 June 2027 is the version-upgrade deadline for 2.4.4 and 2.4.5. For 2.4.6 and 2.4.7 it is 1 June 2028. Third-party software deadlines for 2.4.6 fall earlier, on 30 October 2026 or 31 May 2027.

Is upgrading to 2.4.7 a good stopgap?

Usually not. 2.4.7 regular support ends 31 May 2027. The work to reach 2.4.7 overlaps heavily with reaching 2.4.8 or 2.4.9.

Does extended support apply to Magento Open Source?

Adobe’s lifecycle documentation describes extended support for Adobe Commerce. Open Source merchants should verify that patches are published for their line each month and plan to upgrade.

Sources

• Adobe Commerce released versions and support dates
• Adobe Commerce software lifecycle policy
• Adobe: Required actions and deadlines to secure Commerce environments
• Adobe Commerce release strategy and lifecycle policy FAQ
• Adobe Commerce 2.4.9 release notes
• Critical security update for Adobe Commerce, APSB26-146
• Announcing Mage-OS 3
• Mage-OS releases