Magento 2.4.6 End of Support: What to Do Before 11 August 2026

On 11 August 2026, Magento 2.4.6 reaches the end of its regular support. If you are reading this when it was published, that is a fortnight away.

Most of what has been written about this date says roughly the same thing: support ends, so upgrade now. That advice is not wrong, but it skips the two things that actually determine what you should do. The first is that the deadline does not mean the same thing for every store, because Adobe treats Magento Open Source and Adobe Commerce very differently after this date. The second is that a fortnight is not long enough to upgrade a real store safely, so telling you to “upgrade now” is not a plan.

This article covers what genuinely changes on 11 August, how to work out which side of the line you are on, and what is realistically worth doing in the time that is left. We maintain and upgrade Magento stores for a living, so we have a commercial interest in this topic. We have written it to be useful regardless of who does the work.

Executive Summary

What you will learn: exactly what ends on 11 August 2026, why the answer differs between Magento Open Source and Adobe Commerce, which other versions are expiring at the same time, how long a safe upgrade actually takes, and what to do if you cannot complete one before the date.

Who should read it: store owners, eCommerce managers and IT leads running Magento 2.4.6, 2.4.5 or 2.4.4, and anyone who is not certain which version their store is on.

Why it matters: after a version passes end of support, newly discovered vulnerabilities in it are never fixed. The store keeps working, which is precisely what makes this risk easy to defer. Nothing breaks on 12 August. The exposure simply starts accumulating and never stops.

Effort: around fifteen minutes to establish your position and decide. A full upgrade is typically a 6–14 week project depending on how much custom code and how many extensions you carry.

Key Takeaways

• Magento 2.4.6 regular support ends 11 August 2026. Nothing stops working that day, but security patches stop being issued for that version.
• The critical distinction most coverage blurs: extended support past this date is available to Adobe Commerce customers only. Magento Open Source 2.4.6 gets nothing further.
• If you run Adobe Commerce 2.4.6, you have extended support to 30 August 2027 and more room to plan than the headlines suggest.
• Version 2.4.5 hits the end of its extended support on 12 August 2026, one day later, and 2.4.4 already passed that point on 14 April 2026.
• Two weeks is not enough time to upgrade a real store. Upgrading to 2.4.9 means a server rebuild as much as a code change, because the supported stack moved to PHP 8.5, OpenSearch 3 and Valkey.
• What you can realistically do before the date: confirm your exact version and edition, apply every patch currently available to you, and get a scoped upgrade plan agreed.
• The measurable risk has never been the deadline itself. It is the gap between a patch being published and being applied.

What Actually Happens On 11 August 2026

Nothing visible. Your store does not stop working, your admin panel does not lock, and no warning appears for customers. This is the part that makes the risk so easy to postpone, and it is worth being clear about what does and does not change.

What ends is the flow of fixes. From that date, when a vulnerability is discovered in Magento core code, no patch is produced for the 2.4.6 line. The vulnerability is still published, still discussed publicly, and still exploited. Your store simply never receives the fix. This applies to bug fixes and technical support as well, but security is the part that carries real consequence.

There is also a compliance dimension that tends to surface at the worst moment. Adobe’s own lifecycle documentation flags that running out-of-support software puts PCI compliance at risk. If you take card payments, unsupported software is the kind of thing that becomes a problem during an assessment or, more painfully, during an investigation after an incident. Worth confirming your position with your acquirer or assessor rather than assuming.

The Distinction Almost Every Article Skips

Here is the part that changes what you should actually do, and it is the reason a single deadline produces two very different answers.

Adobe offers an extended support period beyond the standard three year window, which continues to provide quality and security patches for the core application. For 2.4.6 that extended period runs to 30 August 2027, followed by a limited security-only transitional period. That is a full year of additional headroom beyond the date everyone is writing about.

The catch is who qualifies. Extended support is available to Adobe Commerce customers only. It is not available for the Magento Open Source code base. So the same version number produces two entirely different situations:

You May Not Be On The Version You Think

Something worth flagging before you plan around 2.4.6: a large number of stores are on older versions than their owners believe, and two other lines are expiring in the same window.

Version 2.4.5 reached the end of its standard support in August 2025 and its extended support ends on 12 August 2026, one day after 2.4.6. Version 2.4.4 passed the same milestone on 14 April 2026, so stores still on it are already receiving nothing. If you have not upgraded in a couple of years, you are more likely to be in this group than on 2.4.6.

You can confirm your own version from the command line with bin/magento --version, or from the admin panel footer. If neither is available to you, whoever hosts or maintains the store can answer it in under a minute, and an unwillingness to answer it quickly is itself informative. Our guide on how to choose a Magento development agency covers what else that reluctance tends to indicate.

Be Honest About The Timeline: A Fortnight Is Not An Upgrade

Plenty of articles published this month end with “upgrade before 11 August”. For most stores that is not achievable, and pretending otherwise leads to the genuinely dangerous outcome, which is a rushed upgrade pushed straight to production.

A Magento major version upgrade is not a Composer command. Version 2.4.9 moved the supported stack substantially: PHP 8.5, Composer 2.10, MySQL 8.4 or MariaDB 12.3, OpenSearch 3, Valkey 9, RabbitMQ 4.3, Varnish 8 and nginx 1.30. Two of those changes catch teams out badly. Elasticsearch no longer appears in the supported matrix at all, and Redis has been replaced by Valkey. That is infrastructure work sitting underneath the application work.

On top of the platform itself, every third party extension needs a compatible release, every core customisation needs review, and PHP 8.5 will surface deprecations in older custom modules. Then the whole thing needs testing across checkout, payment, shipping, tax, search and any integration you run, on a staging environment that mirrors production.

What You Can Realistically Do Before The Date

Given that, here is what the next fortnight is genuinely good for.

Establish your exact position. Version, patch level and edition, written down. This takes minutes and determines everything else. It also tells you whether you are in the Adobe Commerce group with a further year of cover.

Apply every patch currently available to you. While 2.4.6 is still in support, patches are still being issued for it. Going into the cut-off fully patched is materially better than going in three patches behind, and it is achievable in the time available. This is routine security patch installation work rather than a project.

Get an upgrade scoped, not started. An audit of your extensions, custom modules and integrations tells you whether you are a six week upgrade or a fourteen week one. That number is what lets you plan properly instead of guessing. A Magento code audit is the usual starting point.

Tighten what you control. Admin hardening does not depend on your version: a non-default admin URL, two factor authentication on every account, access restricted by IP or VPN, and removal of accounts belonging to people who have left. Most compromises that begin at the admin panel begin with a credential that should have been deleted long ago.

Choosing Your Target Version

If you are upgrading anyway, the next question is what to upgrade to. There are three defensible answers and the right one depends on your appetite for change.

2.4.9 is the current release and gives you the longest runway, into May 2029. It also demands the most: PHP 8.5, OpenSearch 3 and Valkey mean the infrastructure changes alongside the application. If you are going to do the disruption once, this is the version that buys the most time for it.

2.4.8 is supported to 31 May 2028 and is usually the pragmatic middle. The stack jump is smaller, extension compatibility is broader because the release has been out longer, and you still get a comfortable window before the next decision.

2.4.7 is supported to 31 May 2027. It is a short hop and buys under a year, so it mainly makes sense as a deliberate stepping stone when the gap from your current version is very large and you want to split the work into two smaller, safer moves.

The version most stores should not choose is the one that requires the least work today and the most work in eleven months. Our step by step upgrade walkthrough covers the mechanics, and Magento upgrade services exist for teams who would rather not absorb it internally. Where the store is old enough that upgrading and rebuilding cost something similar, migration is worth pricing as an alternative rather than assuming an in place upgrade is cheapest.

The Real Risk Was Never The Deadline

It is worth putting this date in proportion, because the industry’s actual failure mode is not dramatic expiry. It is ordinary delay.

Security firm Sansec found that roughly 75 percent of Magento and Adobe Commerce stores were still unpatched a week after the fix was published for the vulnerability known as CosmicSting, tracked as CVE-2024-34102. Thousands were subsequently breached. Every one of those stores was on a supported version with a patch available. Support status was not the problem. The gap between publication and application was.

The practical implication is that an upgrade is only half the job. A store on 2.4.9 with nobody responsible for applying patches ends up in the same position as a store on 2.4.6, just more slowly. Ongoing Magento support and maintenance is the part that keeps the benefit of the upgrade.

How This Plays Out By Industry

The deadline is uniform but the pressure is not, and it is worth being realistic about where the difficulty actually sits.

Retail and consumer brands carry the highest extension counts and the strongest seasonal constraints. For retail operations, an upgrade started now lands well before peak trading, whereas one started in September collides with change freezes. The calendar, not the deadline, is the binding constraint.

B2B operations have the most to check, because B2B stores typically run company accounts, shared catalogues, requisition lists and negotiated quotes, plus ERP integration. Several of those capabilities are Adobe Commerce features, which usually means the edition question is already answered, and with it a further year of extended support.

Fashion and apparel stores tend to carry heavy theme customisation and large variant catalogues, so the front end absorbs more of the upgrade effort than the back end. For fashion retailers, theme compatibility is usually the item that sets the timeline.

Logistics and industrial suppliers often have the least visible complexity and the most integration risk, since logistics operations connect to shipping, inventory and pricing systems that must be regression tested as carefully as checkout.

Common Mistakes

Your Pre-Deadline Checklist

How We Can Help

If you want a straight read on where your store stands, that is a short piece of work rather than a project. We can confirm your version, edition and patch level, tell you what a realistic upgrade path and timeline look like for your specific extension footprint, and give you a number you can plan around. If the answer is that you have until 2027, we will tell you that too.

That work spans Magento upgrades, platform migration, security patching, performance audits and ongoing store support, and extends to Adobe Commerce where the licensed edition is the right fit. If you would rather add capacity to your own team than hand the work over, you can hire Magento developers directly.

Talk to us about your upgrade and we will start with your version and your extension list rather than a proposal. You can read more about how we work, look through our client work, or start from our homepage if you are new here.

Related Reading

• How to Choose a Magento Development Agency (2026 Buyer’s Guide)
• Magento: The Complete Guide to Building and Scaling a Store That Performs
• How to Update Magento 2 to the Latest Version
• What the Magento 2.4.9 Release Means for Your Store
• Why Magento 2 Works for B2B Businesses
• Performance Optimisation for Magento 2
• Magento 2 Development in Docker
• Magento for Industrial and Equipment Sellers
• Magento 2 Features Worth Using

Yuvraj Raulji

Verified expert

Founder

Founder of Raulji Technologies with expertise in enterprise eCommerce solutions. Specialized in Magento 2, Shopify, and headless commerce architecture. Driving growth through CRO, SEO, and performance engineering. Helping businesses turn technology into measurable revenue.

View all 92 articles