Magento 2.4 end of support: what to do on 2.4.4 to 2.4.7
Magento 2.4.6 left standard support in August 2026 and Open Source patches now start at 2.4.7. See where each 2.4.x version stands and what to do next.
At the time of writing (November 2026), Adobe gives standard support to Adobe Commerce 2.4.7, 2.4.8 and 2.4.9. Versions 2.4.4, 2.4.5 and 2.4.6 have left standard support and are now in extended or security-only periods, which apply to Adobe Commerce. For Magento Open Source, Adobe's October 2026 security fixes were only published for 2.4.7 and later. If your store runs 2.4.6 or older, and especially if it runs Open Source, it is time to plan an upgrade to 2.4.8 or 2.4.9.
This guide sets out where each 2.4.x version stands, what the recent security bulletins mean, and a practical plan for each situation. It is general information, not security or compliance advice for your specific store.
Where each Magento 2.4 version stands
These dates come from Adobe's Commerce lifecycle policy. Each release gets three years of standard support from general availability. Adobe Commerce 2.4.6 and 2.4.7 get one extra year of extended support, and 2.4.4 to 2.4.6 have a one-time security-only period with isolated security fixes and no quality fixes.
| Version | Released | Standard support ends | Extended support ends | Security-only ends |
|---|---|---|---|---|
| 2.4.4 | 12 April 2022 | 12 April 2025 | 14 April 2026 | 31 May 2027 |
| 2.4.5 | 9 August 2022 | 12 August 2025 | 11 August 2026 | 31 May 2027 |
| 2.4.6 | 14 March 2023 | 11 August 2026 | 31 August 2027 | 31 May 2028 |
| 2.4.7 | 9 April 2024 | 31 May 2027 | 31 May 2028 | Not applicable |
| 2.4.8 | 8 April 2025 | 31 May 2028 | To be confirmed | Not applicable |
| 2.4.9 | 12 May 2026 | 31 May 2029 | To be confirmed | Not applicable |
The lifecycle page is written for Adobe Commerce. Magento Open Source stores should not assume the extended and security-only windows cover them. The practical test is whether Adobe actually publishes fixes for your version, and the latest bulletins answer that clearly.
What the latest security bulletins mean
Two bulletins matter most this autumn:
- APSB26-146 (7 September 2026, priority 1). A critical template engine vulnerability, CVE-2026-75650, rated CVSS 10.0, that needs no authentication and can lead to arbitrary code execution. Adobe said it was aware of the flaw being exploited in the wild. A hotfix is available for Adobe Commerce and Magento Open Source.
- APSB26-153 (13 October 2026, priority 2). Fixes for critical, high and medium vulnerabilities that could lead to arbitrary code execution, privilege escalation, arbitrary file system writes and security feature bypass. Adobe said it was not aware of exploits in the wild.
For APSB26-153, Adobe lists fixed Adobe Commerce builds for every line from 2.4.4 to 2.4.9, using names such as 2.4.9-2026-oct. For Magento Open Source, fixed versions are listed only for 2.4.7, 2.4.8 and 2.4.9. Open Source 2.4.6 is listed as affected with no fixed version, and Adobe's knowledge base confirms Open Source merchants can only download patches for 2.4.7 or later.
A few practical points from Adobe's patch instructions:
- Isolated security patches are tested only against the latest security-only release for your line, for example 2.4.7-p10 or 2.4.8-p5, so you need to be on that version first.
- Earlier monthly isolated patches must be applied in order before the current one.
- The CVE-2026-75650 hotfix is not included in the October isolated patch and must be applied separately.
-
You can check status with
php vendor/bin/patch-status, which reports each CVE as protected, vulnerable or unknown. Adobe notes the tool ships with the July 2026 isolated patch.
If you are on Magento Open Source 2.4.6 or older, you are no longer receiving Adobe's security fixes.
Do not forget PHP and the database
Adobe does not patch third-party components such as PHP, MySQL or MariaDB after they reach end of life, so keeping those supported is your responsibility. This is where older stores often get stuck:
- PHP 8.1 reached end of life on 31 December 2025, and PHP 8.2 follows on 31 December 2026. Adobe's lifecycle page notes this puts PCI compliance at risk for 2.4.4 to 2.4.6.
- According to Adobe's system requirements, the latest 2.4.6 supports PHP 8.2 and 8.1, the latest 2.4.7 supports 8.3 and 8.2, 2.4.8 supports 8.4 and 8.3, and 2.4.9 supports PHP 8.5.
- MySQL 8.0 reached end of support on 30 April 2026, and Adobe recommends moving on-premises databases for 2.4.4 to 2.4.7 to a compatible MariaDB version.
- For Adobe Commerce on Cloud, Adobe says that from 1 June 2027 it will no longer maintain environments running unsupported versions, which can include suspending traffic.
In short, a store on 2.4.6 is tied to PHP versions that are either already unsupported or will be within weeks.
What to do, depending on your version
Magento Open Source 2.4.6 or older
This is the most urgent group. Apply the CVE-2026-75650 hotfix if it is available for your version, put a web application firewall in front of the store, and start an upgrade project to 2.4.8 or 2.4.9 now. Expect extension, theme and PHP work, so budget time for testing.
Adobe Commerce 2.4.4 to 2.4.6
You still receive security fixes during the extended or security-only period, but no quality fixes, and those windows end between May 2027 and May 2028. Use the time to plan a move to 2.4.8 or 2.4.9 well before the Cloud enforcement date.
2.4.7 (either edition)
You are supported until 31 May 2027. Get onto 2.4.7-p10, apply the monthly isolated patches and the hotfix, and plan your next upgrade for 2027. Note that 2.4.7 supports PHP 8.2 and 8.3, and PHP 8.2 loses security support at the end of 2026, so move to 8.3 if you have not already.
2.4.8 or 2.4.9
Keep applying patches as they are released and check the patch status tool after each one.
Whatever your version, a sound upgrade plan includes an inventory of extensions and customisations, compatibility checks with each vendor, a full staging environment, a code freeze during the upgrade, and a rollback plan. Some merchants use this moment to reassess the platform altogether; if that is you, our post on migrating from Magento to Shopify covers that option.
Frequently asked questions
Is Magento Open Source still getting security patches?
Yes, for supported versions. Adobe's October 2026 bulletin includes Open Source fixes for 2.4.7, 2.4.8 and 2.4.9.
What do version names like 2.4.9-2026-oct mean?
Adobe's October bulletin uses these names for the October 2026 fixed builds of each release line. The isolated patch files themselves still require you to be on the latest -p security release for your line.
Can I stay on 2.4.6 for another year?
On Adobe Commerce, 2.4.6 is in extended support until 31 August 2027. On Open Source, Adobe is no longer publishing fixes for it, and its PHP versions are reaching end of life, so staying put carries growing risk.
Need help with your Magento upgrade?
If you need a hand applying patches or planning a move to 2.4.8 or 2.4.9, our Magento development team can audit your extensions, set up staging and handle the upgrade. If you are weighing a platform change instead, read our Magento to Shopify migration guide, or get in touch about Magento maintenance.
Sources: Adobe Commerce lifecycle policy, APSB26-146, APSB26-153, Adobe knowledge base: APSB26-153 patches, Adobe Commerce system requirements, PHP supported versions
(over to you)
Planning a build like this?
Tell us what you're building and we'll come back with ideas and next steps.