Magento Release History and End of Life: Every Version, Every Date

By Scott Bissett  ·  Published: July 23, 2026  ·  Updated: August 12, 2026 — dates re-verified  ·  Reference — every tracked Magento / Adobe Commerce release  ·  Methodology on our accuracy page

The current version of Magento is 2.4.9, released May 12, 2026, with standard support through May 31, 2029. And this page updates on the exact week the previous era ended: Magento 2.4.6 lost standard support on August 11, 2026 — yesterday — and Adobe Commerce 2.4.5's paid extended-support window closes today, August 12, 2026. Two version lines crossed their cliff within 24 hours of each other. For Magento Open Source stores there is no extended tier: a 2.4.6 Open Source store now receives nothing further from Adobe. Adobe Commerce customers on 2.4.6 can continue on extended support to August 30, 2027 — a bridge, at Adobe Commerce prices. That leaves 2.4.7 (standard support to May 31, 2027), 2.4.8 (to May 2028) and 2.4.9 (to May 2029) as the lines with real runway.

Key Dates at a Glance

• Magento 2.4.9: extended support ends 2029-05-31
• Magento 2.4.8: extended support ends 2028-05-31
• Magento 2.4.7: extended support ends 2028-05-31
• Magento 2.4.6: extended support ends 2027-08-30
• Magento 2.4.5: end of life 2024-11-25; extended support ends 2026-08-12
• Magento 2.4.4: end of life 2024-11-25; extended support ends 2026-04-14

Every Magento version: release and end-of-life dates

Release (GA) and support dates for the 2.4.x lines are per Adobe's official lifecycle table, re-verified August 12, 2026; older lines are from our tracked Magento lifecycle data. Each version links to its lifecycle page with live status.

The extended and security-only columns apply to Adobe Commerce (paid) only — Adobe's documentation states extended-support security patches are not available for the Magento Open Source code base. Per our tracked data, the last Open Source security patches for 2.4.4/2.4.5 shipped November 25, 2024. Per-version pages with live status: endoflife.ai/magento.

What is the current version of Magento?

Magento 2.4.9 — released May 12, 2026 for both Adobe Commerce and Magento Open Source, with standard support scheduled through May 31, 2029. Because Adobe ships one full 2.4.x release per year (each May — more on the cadence below), 2.4.9 will remain the newest core version until roughly May 2027. Security patches continue to ship on top of each supported line between full releases, so "current" in practice means 2.4.9 at its latest patch level.

The PHP pairing matters for upgrade planning: per our tracked data, 2.4.9 runs on PHP 8.5, 2.4.8 supports PHP 8.3/8.4, and 2.4.7 supports PHP 8.2/8.3. Stores stuck on old Magento lines are usually stuck on old PHP too — a compounding problem, since PHP versions carry their own end-of-life clocks: see PHP 8.2's December 2026 deadline and the full PHP end-of-life reference.

The three support tiers — and the Open Source / Commerce split

Adobe's lifecycle has three tiers that merchants routinely confuse, and one edition split that decides which dates actually apply to your store:

Standard support ends first — that is the "Standard support ends" column above, and the only column that matters for Magento Open Source. Extended support is a paid Adobe Commerce entitlement carrying security patches further (2.4.6's runs to August 30, 2027). Beyond even that, Adobe's current table lists a security-only period for some lines (2.4.4/2.4.5 through May 31, 2027; 2.4.6 through May 31, 2028). Adobe's documentation is explicit that extended-support patches are not available for the Magento Open Source code base — so an Open Source store's effective deadline is always the earliest column, not the most generous one.

This week made the split concrete: an Adobe Commerce 2.4.6 store has a paid path to August 2027. A Magento Open Source 2.4.6 store hit end of life yesterday.

Why an EOL e-commerce platform is its own category of risk

Unsupported software is a risk everywhere, but a storefront is a special case on two counts:

It processes card data on the open internet. Magecart-style card-skimming campaigns scan industrially for known Magento vulnerabilities — the platform's name is on the technique's original label. An unpatched store isn't a theoretical exposure; it is the exact target profile these campaigns were built to farm. Our Exploited & Unpatchable feed tracks the general pattern: once a version is end of life, actively-exploited vulnerabilities in it never get fixed there.

It has a compliance clock attached. PCI DSS requires protecting systems against known vulnerabilities and applying vendor security patches; a platform whose vendor no longer ships patches cannot demonstrate that, so assessors treat unsupported versions as a direct finding — with card-network consequences, not just audit awkwardness. And for merchants selling into the EU, the regulatory direction is tightening further: see our EU Cyber Resilience Act and EOL compliance explainer.

Magento release schedule and upcoming releases

Adobe publishes the cadence, so no speculation is needed — but the published schedule is also all there is:

• One full 2.4.x release per year, each May. Adobe's release-schedule documentation states a full patch release for the 2.4.x line ships annually in May — 2.4.8 arrived April 2025, 2.4.9 on May 12, 2026. On that cadence, the next full release would be expected around May 2027; Adobe has not published its version number or date.
• One alpha and one beta annually ahead of each full release, for extension and integration testing.
• Security patches at least annually for every supported line — in practice more often, and this is where the support tiers bite: which lines receive them depends on the standard/extended windows in the table above.

Anything beyond that — a "Magento 2.5," new major platforms, dates past 2027 — is not in Adobe's published lifecycle table, and we don't print dates vendors haven't published.

Magento 1: the history questions

Adobe ended support for Magento 1 — both Magento Commerce 1 and Magento Open Source 1 — on June 30, 2020. Every 1.x line from 2008's Magento 1.0 through 1.9 is in the table above. Nothing official has shipped since; the OpenMage community fork maintains the 1.x codebase independently, but from Adobe's (and a PCI assessor's) perspective, a Magento 1 store has been end of life for over six years. Magento 1 stores remained a primary Magecart target well past the cutoff — the longest-running demonstration of why commerce platforms can't coast on EOL software. If the reason vendors do this at all seems arbitrary, it isn't: why end of life is inevitable.

The merchant's checklist

1. On 2.4.6 or older Open Source: you are past end of life as of this week. The upgrade to 2.4.8/2.4.9 is the standard path — smaller than the 2.3→2.4 migrations of years past, but extension compatibility still needs a staging pass.
2. On Adobe Commerce 2.4.6: extended support runs to August 30, 2027 — a real bridge, but a bridge. Use it to schedule the upgrade, not to defer it.
3. Check your tier honestly: Adobe Commerce contracts include extended and security-only windows; Magento Open Source does not — know which dates actually apply to your store before assuming you have runway.
4. PCI reality: unsupported platform versions surface directly in PCI DSS assessments; an EOL Magento isn't just a security risk, it's a compliance finding.

We track Magento and 500+ other products against vendor-verified dates — every Magento version with live status, check any version in seconds, or see what else hits end of life this quarter.

Frequently Asked Questions

Related

• All Magento versions with live status · Magento 2.4.6 — dates and risk score
• PCI DSS and end-of-life software — what assessors actually look for when your platform is unsupported
• PHP 8.2 End of Life and the full PHP EOL reference — the runtime clock underneath every Magento store
• The EU Cyber Resilience Act and EOL software — the regulatory direction for merchants selling into the EU
• Exploited & Unpatchable — the verified feed of KEV-listed vulnerabilities that end-of-life versions will never get fixes for
• Extended support vendors — who patches EOL software commercially, and why end of life is inevitable in the first place