{"id":4001,"date":"2026-11-04T08:27:27","date_gmt":"2026-11-04T08:27:27","guid":{"rendered":"https:\/\/www.magento2-agentur.de\/?p=4001"},"modified":"2026-11-04T08:27:27","modified_gmt":"2026-11-04T08:27:27","slug":"magento-end-of-support-which-versions-are-still-safe-in-2027","status":"publish","type":"post","link":"https:\/\/www.magento2-agentur.de\/en\/magento-end-of-support-which-versions-are-still-safe-in-2027\/","title":{"rendered":"Magento End of Support: Which Versions Are Still Safe in 2027?"},"content":{"rendered":"

Ask most shop owners which Magento version they run and you’ll usually get a shrug. They find out when something breaks. In 2026 that approach started costing real money. Adobe changed how it releases updates, began shipping security fixes every month, and said it can take unsupported Adobe Commerce Cloud stores offline from June 2027.<\/span>\u00a0<\/span><\/p>\n

If you run a small or mid-sized business, the version number now affects decisions well outside IT. It can decide whether you pass a PCI review, whether your ERP connection survives the next patch, and how much you need to set aside for 2027. Below we go through where each Magento 2.4 version stands and what we’d recommend doing about it.<\/span>\u00a0<\/span><\/p>\n

<\/b>Which Magento versions are still supported?<\/span><\/b>\u00a0<\/span><\/h2>\n

Adobe supports every 2.4.x release for three years, counted from its launch date. If you’re on Adobe Commerce, some older versions get a little longer, though only for security fixes. The table shows where each version stood in November 2026, based on Adobe’s lifecycle policy.<\/span>\u00a0<\/span><\/p>\n\n\n\n\n\n\n\n\n\n\n
Version<\/span>\u00a0<\/span><\/td>\nReleased<\/span>\u00a0<\/span><\/td>\nStandard support ends<\/span>\u00a0<\/span><\/td>\nExtra time (Adobe Commerce only)<\/span>\u00a0<\/span><\/td>\nStatus in Nov 2026<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
2.4.9<\/span>\u00a0<\/span><\/td>\nMay 2026<\/span>\u00a0<\/span><\/td>\n31 May 2029<\/span>\u00a0<\/span><\/td>\nNot yet announced<\/span>\u00a0<\/span><\/td>\nCurrent, fully supported<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
2.4.8<\/span>\u00a0<\/span><\/td>\nApril 2025<\/span>\u00a0<\/span><\/td>\n31 May 2028<\/span>\u00a0<\/span><\/td>\nNot yet announced<\/span>\u00a0<\/span><\/td>\nFully supported<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
2.4.7<\/span>\u00a0<\/span><\/td>\nApril 2024<\/span>\u00a0<\/span><\/td>\n31 May 2027<\/span>\u00a0<\/span><\/td>\nExtended support to 31 May 2028<\/span>\u00a0<\/span><\/td>\nSupported, plan upgrade for 2027<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
2.4.6<\/span>\u00a0<\/span><\/td>\nMarch 2023<\/span>\u00a0<\/span><\/td>\nEnded 11 Aug 2026<\/span>\u00a0<\/span><\/td>\nExtended to 31 Aug 2027, security-only to 31 May 2028<\/span>\u00a0<\/span><\/td>\nExtended support only<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
2.4.5<\/span>\u00a0<\/span><\/td>\nAugust 2022<\/span>\u00a0<\/span><\/td>\nEnded Aug 2025<\/span>\u00a0<\/span><\/td>\nSecurity-only to 31 May 2027<\/span>\u00a0<\/span><\/td>\nCritical fixes only<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
2.4.4<\/span>\u00a0<\/span><\/td>\nApril 2022<\/span>\u00a0<\/span><\/td>\nEnded April 2025<\/span>\u00a0<\/span><\/td>\nSecurity-only to 31 May 2027<\/span>\u00a0<\/span><\/td>\nCritical fixes only<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
2.4.0\u20132.4.3, Magento 1<\/span>\u00a0<\/span><\/td>\n2020 and earlier<\/span>\u00a0<\/span><\/td>\nEnded<\/span>\u00a0<\/span><\/td>\nNone<\/span>\u00a0<\/span><\/td>\nUnsupported, migrate now<\/span>\u00a0<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/b>On Magento Open Source?<\/span><\/b> Be careful with the extra time in the table.<\/span> Adobe describes the extended and security-only periods for Adobe Commerce customers, and its 2026 security bulletins only covered Open Source versions 2.4.6 to 2.4.9. We’d plan around the standard support date and leave it at that.<\/span>\u00a0<\/span><\/p>\n

<\/b>Don’t know your version?<\/span><\/b> Look at the footer of the Magento admin, or ask your developer to run <\/span>bin\/magento –version<\/span> on the server.<\/span>\u00a0<\/span><\/p>\n

<\/b>What does “end of support” mean in practice?<\/span><\/b>\u00a0<\/span><\/h3>\n

Nothing happens to your shop on the day support ends. It keeps running. What stops is the fixes, and over time that turns into four problems for the business, not just for whoever looks after the server.<\/span>\u00a0<\/span><\/p>\n

    \n
  1. Security holes stay open.<\/span><\/b> Vulnerabilities found after the deadline don’t get patched on your version. Adobe’s 2026 bulletins show why that matters. In July it fixed a webhook flaw that let attackers run code without logging in, and in September it pushed out an emergency hotfix for a zero-day that was already being exploited.<\/span><\/li>\n
  2. Audits get harder.<\/span><\/b> Taking card payments brings PCI DSS into play, and PCI expects software that is supported and patched. GDPR Article 32 also asks you to protect customer data with appropriate technical measures. An unpatched shop is hard to defend in either review, and cyber insurers ask about it more and more.<\/span><\/li>\n
  3. PHP has its own deadlines.<\/span><\/b> PHP 8.1 reached end of life on 31 December 2025 and PHP 8.2 follows on 31 December 2026. A 2.4.6 store on PHP 8.2 therefore hits two deadlines a few weeks apart. Magento 2.4.9, by comparison, runs on PHP 8.5.<\/span><\/li>\n
  4. Cloud stores can be switched off.<\/span><\/b> From 1 June 2027, Adobe will stop maintaining Adobe Commerce Cloud environments on unsupported versions and may suspend their traffic. For 2.4.4 and 2.4.5 that date is 1 June 2027. For 2.4.6 and 2.4.7 it’s 1 June 2028.<\/span><\/li>\n<\/ol>\n

    One more thing tends to catch people out. Extension vendors and integration partners gradually stop testing against old versions. Then one day your payment module or ERP connector gets an update and simply stops working on your release.<\/span>\u00a0<\/span><\/p>\n

    <\/b>How often does Adobe patch Magento now?<\/span><\/b>\u00a0<\/span><\/h3>\n

    Adobe moved to a fixed schedule in 2026. A major release comes out each May. Bundled security patches, the versions ending in “-p”, follow in May and November. Smaller, isolated security fixes can appear on the second Tuesday of any month, and a critical hotfix can come out on any day.<\/span>\u00a0<\/span><\/p>\n

    So patching is now a monthly job rather than a yearly one. A simple routine looks like this:<\/span>\u00a0<\/span><\/p>\n

      \n
    1. On the second Tuesday of each month, read Adobe’s security bulletin.<\/span>\u00a0<\/span><\/li>\n<\/ol>\n
        \n
      1. Install the fixes that apply to you on a staging copy of the shop, not the live site.<\/span>\u00a0<\/span><\/li>\n<\/ol>\n
          \n
        1. Test the parts that make money: checkout, payment, customer login and B2B quotes.<\/span>\u00a0<\/span><\/li>\n<\/ol>\n
            \n
          1. Test every integration, above all the order export to your ERP.<\/span>\u00a0<\/span><\/li>\n<\/ol>\n
              \n
            1. Go live, then write down the patch level, the date and who did it.<\/span>\u00a0<\/span><\/li>\n<\/ol>\n

              Step 4 is the one SMEs skip most often. When the shop is connected to SAP Business One, a core patch can change how an API behaves, and the connector depends on that behaviour. After every update, place a test order and check that it reaches the ERP and that stock levels and customer prices come back correctly. Glancing at the storefront won’t tell you that.<\/span>\u00a0<\/span><\/p>\n

              The next bundled patch, 2.4.9-p1, is due this month (November 2026). If you’re already on 2.4.9, book a short test window for it now.<\/span>\u00a0<\/span><\/p>\n

              <\/b>Patch, upgrade or rebuild?<\/span><\/b>\u00a0<\/span><\/h3>\n

              Your version number matters less than what has been built on top of it, meaning custom code and extensions. Use the table as a rough guide and adjust it to your own setup.<\/span>\u00a0<\/span><\/p>\n\n\n\n\n\n\n\n\n\n
              If you run<\/span>\u00a0<\/span><\/td>\nDo this<\/span>\u00a0<\/span><\/td>\nWhen<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
              2.4.9<\/span>\u00a0<\/span><\/td>\nApply the monthly fixes and install 2.4.9-p1<\/span>\u00a0<\/span><\/td>\nOngoing<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
              2.4.8<\/span>\u00a0<\/span><\/td>\nKeep patching and plan the move to 2.4.9<\/span>\u00a0<\/span><\/td>\nPlan in H1 2027<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
              2.4.7<\/span>\u00a0<\/span><\/td>\nMove to 2.4.9 before standard support ends<\/span>\u00a0<\/span><\/td>\nStart Q1 2027, finish before 31 May 2027<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
              2.4.6<\/span>\u00a0<\/span><\/td>\nUpgrade now, and sort out PHP 8.2 first<\/span>\u00a0<\/span><\/td>\nQ4 2026 \u2013 Q1 2027<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
              2.4.4 or 2.4.5<\/span>\u00a0<\/span><\/td>\nGet quotes for both an upgrade and a rebuild<\/span>\u00a0<\/span><\/td>\nFinish before 31 May 2027<\/span>\u00a0<\/span><\/td>\n<\/tr>\n
              2.4.3 or older, Magento 1<\/span>\u00a0<\/span><\/td>\nPlan a full replatform<\/span>\u00a0<\/span><\/td>\nStart immediately<\/span>\u00a0<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

              <\/b>When is a rebuild the better choice?<\/span><\/b> Look at it seriously if your theme is a heavily customised Luma, if half your extensions are no longer maintained, or if the upgrade quote comes close to the price of a new build.<\/span> Hyv\u00e4 has been free and open source since November 2025, so a fast, modern frontend costs far less than it used to. A rebuild is also a good chance to tidy up the ERP integration instead of dragging old workarounds into the new shop.<\/span>\u00a0<\/span><\/p>\n

              <\/b>What makes an upgrade expensive?<\/span><\/b> In the projects we’ve worked on, it usually comes down to three things:<\/span>\u00a0<\/span><\/p>\n

                \n
              • <\/b>Third-party extensions:<\/span><\/b> every one has to be checked against 2.4.9 and PHP 8.5. Version 2.4.9 replaced several framework components, so older modules break more often than you’d expect.<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                  \n
                • <\/b>Custom modules:<\/span><\/b> code written for earlier versions may need reworking.<\/span>\u00a0<\/span><\/li>\n<\/ul>\n
                    \n
                  • <\/b>Integrations:<\/span><\/b> ERP, payment, shipping and PIM connections all need a full round of regression testing.<\/span>\u00a0<\/span><\/li>\n<\/ul>\n

                    Get a free Magento version check<\/span><\/b>\u00a0<\/span><\/h3>\n

                    Not sure how close you are to a deadline? Ingold Solutions will check your Magento version, PHP runtime, extensions and SAP Business One integration, then give you a clear upgrade path and a fixed quote. As an Adobe Solution Partner and SAP Partner, we handle the shop upgrade and the ERP connection in one project, so the two keep working together.<\/span>\u00a0<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                    Ask most shop owners which Magento version they run and you’ll usually get a shrug. They find out when something breaks. In 2026 that approach started costing real money. Adobe changed how it releases updates, began shipping security fixes every month, and said it can take unsupported Adobe Commerce Cloud stores offline from June 2027.\u00a0 […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[17,18],"tags":[],"class_list":["post-4001","post","type-post","status-publish","format-standard","hentry","category-magento-2","category-magento-b2b-en"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t