The current Magento version is 2.4.9, which Adobe released on May 12, 2026 for both Magento Open Source and Adobe Commerce. If your store runs anything older, the question that matters is not which version is newest but how long your version will keep getting security fixes. That date drives your upgrade budget, your PCI conversations and, on Adobe Commerce Cloud, whether Adobe keeps serving your storefront at all.
This guide lists every Magento 2.4 release line with its release date and end-of-support dates, taken from Adobe's published lifecycle policy as of October 14, 2026, and explains what each date means in practice. If you are already past a deadline, our Magento migration services team handles version upgrades as well as full replatforms, and our Magento support services keep a store patched between upgrades.
What is the current Magento version?
Magento 2.4.9 is the newest generally available release, published May 12, 2026. Adobe ships Magento Open Source and Adobe Commerce on the same version numbers on the same day, so "Magento 2.4.9" means the same core codebase whichever edition you run.
Two other releases are worth knowing about:
- 2.4.8-p5 is the latest patch for the 2.4.8 release line, also released May 12, 2026. If you are on 2.4.8, this is the version you should be running.
- 2.4.10-alpha1 was released October 13, 2026. It is a pre-release for testing extensions and code, not a production version.
2.4.9 also moves the PHP baseline. Adobe's system requirements list PHP 8.5 for 2.4.9, with PHP 8.4 allowed for upgrade purposes only, and the 2.4.9 release notes state that PHP 8.2 and 8.3 are no longer supported. Plan the PHP upgrade together with the Magento upgrade, because it is often the bigger job for older extensions.
Magento 2.4 release dates and end-of-support dates
Adobe gives every release line three years of standard support from its general availability date. Some older lines also get extended support and a security-only period. Here is the full schedule from Adobe's lifecycle policy:
| Release line | Released | End of standard support | End of extended support | End of security-only period |
|---|---|---|---|---|
| 2.4.9 | May 12, 2026 | May 31, 2029 | To be announced | Not applicable |
| 2.4.8 | April 8, 2025 | May 31, 2028 | To be announced | Not applicable |
| 2.4.7 | April 9, 2024 | May 31, 2027 | May 31, 2028 | Not applicable |
| 2.4.6 | March 14, 2023 | August 11, 2026 | August 31, 2027 | May 31, 2028 |
| 2.4.5 | August 9, 2022 | August 12, 2025 | August 11, 2026 | May 31, 2027 |
| 2.4.4 | April 12, 2022 | April 12, 2025 | April 14, 2026 | May 31, 2027 |
Releases 2.4.0 through 2.4.3 are long out of support: Adobe's released versions page shows regular support for that line ended on November 28, 2022. If you are still on one of them, or on Magento 1, treat it as an urgent migration rather than a routine upgrade.
As of today, that leaves three release lines in standard support (2.4.7, 2.4.8 and 2.4.9), one in extended support (2.4.6) and two in the security-only period (2.4.4 and 2.4.5).
How Adobe's support tiers work
The lifecycle policy defines three tiers, and they are not equal:
- Standard support runs for three years from release. It includes quality fixes, security patches and full Adobe Commerce support. This is the only tier you should plan to run a production store on long term.
- Extended support is one extra year at no cost, which Adobe offers to Adobe Commerce customers on 2.4.6 and 2.4.7. It covers quality and security patches for the core application. Extended support for 2.4.4 and 2.4.5 has already ended.
- The security-only transitional period applies only to 2.4.4, 2.4.5 and 2.4.6. It provides limited, isolated security fixes and no quality fixes. Adobe calls it a one-time exception that will not be extended, and tells customers to treat it as migration time, not as a support tier.
A practical consequence: a store in the security-only period can still receive fixes for critical vulnerabilities, but nothing else gets fixed. Bugs in checkout, indexing or the admin stay broken.
Every date in this post comes from Adobe Experience League: the Adobe Commerce lifecycle policy (last updated September 18, 2026), the released versions page and the patch release schedule. Adobe revises these pages, so check them before you commit budget. Links are listed at the end of the post.
Does Magento Open Source get the same dates?
Magento Open Source ships on the same version numbers and the same release days as Adobe Commerce, and patches are published for both editions. The lifecycle policy, however, is written for Adobe Commerce, and its extended support offer is described as being for Adobe Commerce customers.
So if you run Magento Open Source, plan around the end of standard support date for your release line, and do not count on the extended or security-only windows. For a 2.4.6 Open Source store, that means the safe assumption is that support ended on August 11, 2026. If you are weighing whether the licensed edition is worth it for the longer support window and the commercial features, our Magento Open Source vs Adobe Commerce comparison covers the trade-offs.
Adobe Commerce on Cloud: the enforcement dates
Cloud customers have a harder deadline than everyone else. Adobe's lifecycle policy introduces an enforced version upgrade policy for Adobe Commerce on Cloud. Starting June 1, 2027, Adobe says it will no longer maintain Cloud environments running unsupported Commerce versions and may suspend traffic to affected infrastructure, which takes the storefront offline.
The policy table lists these Cloud deadlines:
- 2.4.4 and 2.4.5: June 1, 2027
- 2.4.6 and 2.4.7: June 1, 2028
- 2.4.8 and 2.4.9: to be announced
Adobe also warns that environments which stay non-compliant after a traffic suspension may be decommissioned, with data deleted. If you run 2.4.4 or 2.4.5 on Cloud, you have until spring 2027 to finish an upgrade or a move to Adobe Commerce as a Cloud Service, Adobe's SaaS edition, which Adobe now recommends as the long-term destination for Cloud customers.
PHP end of life is a second deadline
Your Magento version and your PHP version expire separately. Adobe's lifecycle page flags two PHP dates with PCI implications:
- PHP 8.1 reached end of life on December 31, 2025. It affects 2.4.4, 2.4.5 and 2.4.6 where 8.1 is still in use.
- PHP 8.2 reaches end of life on December 31, 2026. It affects 2.4.6 where 8.2 is used, and Adobe advises planning the upgrade before the end of 2026.
Adobe also notes that it does not fix third-party dependencies such as PHP, MariaDB, OpenSearch, Redis, Valkey or RabbitMQ. Even inside a supported Magento window, you are responsible for keeping those services on supported versions. PCI compliance is assessed by the merchant, so share these dates with your qualified security assessor.
The latest patch for each release line
Being on a supported release line is not enough. Adobe recommends running the latest security patch for your line, and isolated security patch files are only tested against the latest -p version. These were the newest patches as of October 14, 2026:
| Release line | Latest patch | Released |
|---|---|---|
| 2.4.9 | 2.4.9 | May 12, 2026 |
| 2.4.8 | 2.4.8-p5 | May 12, 2026 |
| 2.4.7 | 2.4.7-p10 | May 12, 2026 |
| 2.4.6 | 2.4.6-p15 | May 12, 2026 |
| 2.4.5 | 2.4.5-p17 | May 12, 2026 |
| 2.4.4 | 2.4.4-p18 | May 12, 2026 |
How Adobe ships Magento releases now
Adobe's patch release schedule describes four kinds of release:
- A full patch for the 2.4.x release line once a year, in May. 2.4.8 and 2.4.9 both followed this pattern.
- Security patches for every supported release line at least once a year. They roll up previous security, compliance and quality hotfixes.
- Isolated security patch files, released independently between security patches for faster fixes. To apply one, you must already be on the latest security patch for your line.
- One alpha and one beta per year for testing the next release, which is why 2.4.10-alpha1 appeared in October.
In practice, that means budgeting for at least one planned patch cycle a year, staging every patch before production, and keeping the ability to apply an isolated security fix within days when Adobe publishes one.
What to do based on the version you run
2.4.0 to 2.4.3, or Magento 1. You are years past support. Scope a migration now, and decide whether you are staying on Magento or moving platforms before you spend on fixes.
2.4.4 or 2.4.5. Extended support is over. You are in the security-only period until May 31, 2027, with no quality fixes. On Cloud, your enforcement date is June 1, 2027. Start the upgrade to 2.4.8 or 2.4.9 this quarter. Most of the effort will be extension compatibility and PHP.
2.4.6. Standard support ended August 11, 2026. Adobe Commerce customers have extended support to August 31, 2027. Your PHP 8.2 runtime reaches end of life at the end of 2026, which is the more urgent date. Open Source stores should treat 2.4.6 as unsupported.
2.4.7. Supported until May 31, 2027, with extended support to May 31, 2028 for Adobe Commerce. Plan an upgrade in 2027 rather than waiting for the extended window.
2.4.8 or 2.4.9. You are in good shape. Stay on the latest patch, keep PHP and services current, and test 2.4.10 when the beta arrives.
Whichever line you are on, the effort is driven less by the Magento version jump than by custom modules, third-party extensions and the PHP move, so audit those first.
How to check which Magento version you are running
You have three quick options:
- The Admin. The footer of the Magento Admin shows the version, for example "Magento ver. 2.4.7-p10".
- The command line. From the Magento root, run
bin/magento --version. - Composer. Check the installed version of the
magento/product-community-editionpackage (Open Source) ormagento/product-enterprise-editionpackage (Adobe Commerce) incomposer.lock.
Sources
- Adobe Commerce lifecycle policy, Adobe Experience League, last updated September 18, 2026
- Released versions, Adobe Experience League
- Patch release schedule, Adobe Experience League, last updated October 8, 2026
- System requirements, Adobe Experience League
Not sure how far behind your store is?
We will check your version, extensions and PHP runtime against Adobe's support dates and give you a clear upgrade path and a firm quote.
Book a 30-minute assessmentFrequently asked questions
What is the latest Magento version?
The latest Magento version is 2.4.9, released May 12, 2026 for Magento Open Source and Adobe Commerce. The newest patch on the previous line is 2.4.8-p5. Adobe also released 2.4.10-alpha1 on October 13, 2026, but alpha releases are for testing, not production stores.
When does Magento 2.4.6 support end?
Standard support for 2.4.6 ended August 11, 2026. Adobe Commerce customers get extended support until August 31, 2027 and a security-only period until May 31, 2028. Magento Open Source merchants should plan around the August 11, 2026 date.
How long is a Magento version supported?
Adobe supports each 2.4.x release line for three years from its general availability date. Adobe Commerce customers on 2.4.6 and 2.4.7 get one extra year of extended support at no cost, and 2.4.4, 2.4.5 and 2.4.6 have a one-time security-only period after that.
Is Magento 2.4.7 still supported?
Yes. Standard support for 2.4.7 runs until May 31, 2027, and Adobe Commerce customers have extended support until May 31, 2028. Make sure you are on the latest patch, which was 2.4.7-p10 as of October 2026.
Which PHP version does Magento 2.4.9 need?
Adobe lists PHP 8.5 for Magento 2.4.9, with PHP 8.4 allowed for upgrade purposes only. PHP 8.2 and 8.3 are not supported on 2.4.9, so stores on older PHP need a runtime upgrade as part of the move.
What happens if my Adobe Commerce Cloud store stays on an unsupported version?
Adobe says that from June 1, 2027 it will no longer maintain Cloud environments running unsupported versions and may suspend traffic to them, which takes the storefront offline. Environments that stay non-compliant may be decommissioned. The Cloud deadline is June 1, 2027 for 2.4.4 and 2.4.5 and June 1, 2028 for 2.4.6 and 2.4.7.