Adobe Commerce 2.4.5 extended support and 2.4.6 standard support ended 11 August 2026

Update, 14 September 2026: a separate and more urgent matter sits alongside these support dates. Adobe published Security Bulletin APSB26-146 on 7 September for CVE-2026-75650, a vulnerability it says is being exploited in the wild, and updated its remediation guidance on 11 September. If your store has not been patched and its credentials rotated, that comes before any support-date planning: what to verify after the APSB26-146 hotfix.

Adobe’s lifecycle table puts two Adobe Commerce support deadlines on the same date: Adobe Commerce 2.4.5 extended support ended on 11 August 2026, and Adobe Commerce 2.4.6 standard support ended on 11 August 2026. If that date brought you here, /migrate/magento/ is where to start a version and extension review.

Staying on Adobe Commerce can still be the right answer. Adobe Commerce 2.4.7, 2.4.8, and 2.4.9 remain inside published support windows. The decision is whether the upgrade path is smaller than the work required to move the store onto a different commerce stack.

The 11 August support overlap

Adobe’s lifecycle policy, read on 3 September 2026, gives this table:

Release	General availability	Standard support ends	Extended support ends	Security-only ends	Cloud enforcement
Adobe Commerce 2.4.9	12 May 2026	31 May 2029	TBD	N/A	TBD
Adobe Commerce 2.4.8	8 April 2025	31 May 2028	TBD	N/A	TBD
Adobe Commerce 2.4.7	9 April 2024	31 May 2027	31 May 2028	N/A	1 June 2028
Adobe Commerce 2.4.6	14 March 2023	11 August 2026	31 August 2027	31 May 2028	1 June 2028
Adobe Commerce 2.4.5	9 August 2022	12 August 2025	11 August 2026	31 May 2027	1 June 2027
Adobe Commerce 2.4.4	12 April 2022	12 April 2025	14 April 2026	31 May 2027	1 June 2027

The paired deadline matters because 2.4.5 and 2.4.6 are in different states after the same day. Adobe Commerce 2.4.5 has left extended support and is in the security-only transitional period. Adobe Commerce 2.4.6 has left standard support and moved into extended support, which Adobe says includes quality and security patches for the core application.

The no-cost extension is for 2.4.6 and 2.4.7

Adobe’s current lifecycle policy says Adobe offers one year of additional support at no additional cost for Adobe Commerce customers on versions 2.4.6 and 2.4.7. The same paragraph says extended support for Adobe Commerce 2.4.4 and 2.4.5 ends in April and August 2026 as planned.

That distinction decides the first conversation. A 2.4.6 estate is past standard support, with extended support still published through 31 August 2027. A 2.4.5 estate is past extended support, with only the security-only transitional period left in the Adobe table.

Security-only means isolated security fixes

Adobe describes the security-only transitional period as one-time, time-limited, and available only for 2.4.4, 2.4.5, and 2.4.6 release lines whose extended support ended in 2025 or 2026. It provides limited isolated security fixes only, with no quality fixes.

Adobe also says the period will not be extended beyond the published dates. For 2.4.5, that date is 31 May 2027. For 2.4.6, it is 31 May 2028.

Cloud enforcement starts 1 June 2027

Adobe’s lifecycle page adds a Cloud-only enforcement date. Starting 1 June 2027, Adobe says it will stop maintaining Cloud environments that run unsupported Commerce versions and will take action to protect the platform and customers. Adobe’s own warning includes “suspending traffic to the affected infrastructure.”

In the table, Adobe Commerce 2.4.5 and 2.4.4 carry the first Cloud enforcement date: 1 June 2027. Adobe Commerce 2.4.6 and 2.4.7 carry 1 June 2028. Adobe Commerce 2.4.8 and 2.4.9 are still listed as TBD.

Magento Open Source is a separate support question

Adobe’s lifecycle policy is written for Adobe Commerce. Its no-cost extension paragraph is worded for Adobe Commerce customers, and its enforced-upgrade paragraph is worded for Adobe Commerce on Cloud.

The policy gives no equivalent support-extension or sunset statement for Magento Open Source. Magento Open Source stores still need a version, patch, PHP, dependency, hosting, and security review, but this Adobe Commerce lifecycle table should not be restated as a new Magento Open Source sunset.

Upgrade first, price migration where the upgrade is bigger

For a maintained Adobe Commerce estate, the shortest responsible path may be an in-place upgrade to a supported release line or, for Cloud customers, Adobe Commerce as a Cloud Service. That keeps the store inside Adobe’s published support model.

The migration question starts when the version upgrade exposes the work the store has been carrying: extension risk, checkout customisation, search and merchandising logic, payment and fulfilment integrations, or a storefront that needs deeper ownership than another platform cycle gives it.

Our Magento to Medusa migration guide covers the commerce mechanics: catalogue export, product and variant mapping, order history policy, extension rebuilds, and URL preservation. Medusa.js development is the service page for teams already choosing a Medusa-led rebuild.

If you are on Adobe Commerce 2.4.5 or 2.4.6, start with /migrate/magento/. Bring the release line, edition, Cloud or self-hosted status, extension list, checkout customisations, and the support date you are planning against. WAYF can scope the upgrade-versus-migration decision before anyone commits to a platform move.

FAQ

1. When did Adobe Commerce 2.4.6 standard support end?

   Adobe's lifecycle policy lists 11 August 2026 as the end of standard support for Adobe Commerce 2.4.6. Extended support runs to 31 August 2027, the security-only period runs to 31 May 2028, and Cloud version enforcement is dated 1 June 2028.

2. When did Adobe Commerce 2.4.5 extended support end?

   Adobe's lifecycle policy lists 11 August 2026 as the end of extended support for Adobe Commerce 2.4.5. The security-only period runs to 31 May 2027, and the Cloud-only version enforcement date is 1 June 2027.

3. Which Adobe Commerce versions get the no-cost support extension?

   Adobe's lifecycle policy says Adobe offers one year of additional support at no additional cost for Adobe Commerce customers on versions 2.4.6 and 2.4.7. The same paragraph says extended support for Adobe Commerce 2.4.4 and 2.4.5 ends in April and August 2026 as planned.

4. What is the Adobe Commerce security-only transitional period?

   Adobe describes it as a one-time, time-limited period for versions 2.4.4, 2.4.5, and 2.4.6 whose extended support ended in 2025 or 2026. It provides limited isolated security fixes only, with no quality fixes, and Adobe says it will not be extended beyond the published dates.

5. Does this mean Magento Open Source has a new sunset date?

   No. Adobe's lifecycle policy is written for Adobe Commerce and gives no equivalent support-extension or sunset statement for Magento Open Source. Treat Magento Open Source support as a separate source question.

6. Should a team on Adobe Commerce 2.4.5 or 2.4.6 migrate now?

   An in-place upgrade to a supported Adobe Commerce line can be the correct move when the extension stack is maintained and the store still fits the platform. Migration belongs on the table when the upgrade lift, Cloud enforcement, or custom commerce logic makes another rebuild cycle larger than a move.

Sources

• Adobe Commerce lifecycle policy - the support windows, security-only period, and Cloud enforcement dates, read 3 September 2026
• Adobe Commerce released versions - per-release-line support notes for Adobe Commerce 2.4.5 and 2.4.6, read 3 September 2026. Its support-extension note still names 2.4.4 and 2.4.5; the lifecycle policy, updated later, is the current statement.
• WAYF, Magento to Medusa migration guide - the migration mechanics for Adobe Commerce and Magento Open Source stores
• WAYF, Magento migration review - the starting point for scoping a Magento or Adobe Commerce move
• WAYF, Medusa.js development - the Medusa service page for commerce rebuilds