Magento
How long will Magento 2 still be supported?
Short answer
Magento 2 as a platform has no end date; Adobe releases a new version every year. Each version on its own is supported for a limited number of years, though. In October 2026, 2.4.7, 2.4.8 and 2.4.9 still receive security patches. For 2.4.6 and older, regular support has ended. If your shop runs on such an older version, newly found holes stay open and an upgrade is needed.
How does Magento support work?
Adobe has recently moved to one new version a year, in the spring. Each version gets patches for a number of years. On top of that, security patches appear through the year for all versions that are still supported.
| Version | Released | Status in October 2026 |
|---|---|---|
| 2.4.9 | May 2026 | Supported, into 2029 |
| 2.4.8 | April 2025 | Supported, into 2028 |
| 2.4.7 | April 2024 | Supported, into 2027 |
| 2.4.6 | March 2023 | Regular support ended in August 2026 |
| 2.4.5 and older | 2022 and earlier | No longer supported |
| Magento 1 | 2008 | Stopped in June 2020 |
Adobe adjusts this schedule now and then. The current dates are in Adobe’s support policy; check them before you make a plan.
What does “no longer supported” mean?
That Adobe no longer makes patches for that version. The shop keeps working. Orders come in, customers notice nothing.
What changes is that a newly found hole in that version stays open. With Magento, holes are not theory: automated attacks look for shops that miss the patch within days of an announcement. The usual target is the checkout page, where a piece of added code reads payment details along.
On top of that, the components underneath get stuck. An old Magento version only works with an old PHP version, and that in turn gets no more updates. Hosts switch such versions off.
What else do you notice with an old version?
- Payment providers set requirements. Anyone who processes card payments has to meet the card schemes’ requirements, and current software is part of that.
- Modules stop being updated. Makers support the versions that Adobe supports.
- Every repair costs more. A developer first has to work out how something behaved in that old version.
- The jump gets bigger. The longer you wait, the more changes at once.
What do you do if your shop is behind?
- Establish where you stand. Version, patch level, PHP version, and which modules run.
- Install the patches that still exist for your version. That buys time and is small work.
- Plan the upgrade to a version that will last for years. In a test environment, with a trial run.
- Check modules and theme. What has no successor, you replace or build again.
- Then agree a rhythm. Patches as soon as they come out, one version up each year.
An upgrade is also the moment to clear out: modules nobody uses, an outdated theme, a slower search engine. Some shops switch to Hyvä at the same time.
What the work involves is covered under Magento upgrade. If you first want to know how the shop stands, start with a Magento audit. And keeping up is part of maintenance and support.