Magento 2.4.6 Support Ends on 11 August. Why Open Source and Adobe Commerce Stores Face Completely Different Deadlines

Most articles about the Magento 2.4.6 end of support deadline say the same thing. Support ends, so upgrade now.

That advice is not wrong, but it skips the question that actually determines what you should do this month. Adobe treats Magento Open Source and Adobe Commerce very differently after 11 August, and the gap between them is roughly two years. If nobody has told you which side of that line your store sits on, you cannot plan anything sensibly.

So let us start there.

What the Magento 2.4.6 end of support date actually means

Nothing breaks.

Your store keeps running. Orders keep processing. Payments keep clearing. Nobody flips a switch and no warning banner appears in your admin panel.

What stops is Adobe issuing patches for that version. From that date, when a security vulnerability is found in Magento core code, stores on 2.4.6 do not get a fix. The vulnerability gets documented publicly, because that is how responsible disclosure works, and your store stays open to it permanently.

That is the real change behind the Magento 2.4.6 end of life headlines. Not a shutdown, but the quiet transfer of responsibility for your store's security from Adobe to you. It is the same pattern we wrote about when Google shut down the Content API for Shopping: the failure is silent, which is exactly why merchants find out late.

The split that decides everything

Adobe gives every version three years of standard support from its general availability date. Magento 2.4.6 went generally available on 14 March 2023, which is where 11 August 2026 comes from.

After standard support, Adobe offers extended support: one year of additional quality and security patches at no extra cost. For the 2.4.6 and 2.4.7 lines, that extension exists.

Here is the part most coverage leaves out. Adobe's lifecycle policy states that extended support is offered to Adobe Commerce customers. It does not cover the Magento Open Source code base. There is no Magento Open Source extended support tier at all.

So the same version number produces two completely different outcomes:

If you run Magento Open Source, 11 August is your date and there is nothing behind it. If you are a licensed Adobe Commerce customer, you have considerably more room than the Magento end of life August 2026 headlines suggest.

How to check which edition you are running in thirty seconds

If you are unsure, the fastest way to tell is your billing. Adobe Commerce is a paid licence, invoiced annually, usually in the five or six figure range. If nobody at your company is paying Adobe a licence fee, you are on Magento Open Source and the Magento 2.4.6 end of support date is your hard deadline.

You can also ask your developer to run bin/magento --version on the server, which returns both the edition and the exact patch level. The current patch release for the 2.4.6 line is 2.4.6-p15, issued on 12 May 2026.

Adobe Commerce 2.4.6 support runs on three dates, not one

If you do hold a licence, it is worth understanding the full shape of what Adobe offers, because the three tiers are not equivalent and most summaries collapse them into one.

Standard support, ending 11 August 2026, includes quality fixes, security patches and Adobe on-call support. It also includes hotfixes for critical zero-day vulnerabilities, which Adobe provides to any customer on a supported version even if they are not running the latest patch.

Extended support, running to 30 August 2027, includes quality and security patches for the core application. This is a genuine continuation of Adobe Commerce 2.4.6 support, not a token gesture.

The security-only transitional period, running to 31 May 2028, is different in kind. Adobe describes it as providing limited isolated security fixes only. Quality fixes stop. Adobe is unusually direct about how to read it, stating that it is a one-time exception, that it will not be extended beyond the published dates, and that merchants should treat it as migration time rather than a long-term support tier.

In plain terms, the final twenty months of that timeline are a runway, not a resting place.

There is one more date if you run Adobe Commerce on Cloud. Adobe has introduced an enforced version upgrade policy and lists 1 June 2028 as the version upgrade enforcement date for the 2.4.6 line. After that date, Adobe will no longer maintain Cloud environments running unsupported versions and reserves the right to decommission them.

The compliance problem that has nothing to do with 11 August

This is the part almost nobody writes about, and for many stores it is more urgent than the Magento 2.4.6 end of life date itself.

Adobe's lifecycle policy carries a section on PHP end of life and PCI compliance. It notes that PHP 8.1 reached end of life on 31 December 2025, affecting the 2.4.4, 2.4.5 and 2.4.6 lines wherever PHP 8.1 is in use. Adobe's own assessment is that running PHP 8.1 past its end-of-life date puts PCI compliance at risk, because vulnerabilities in PHP itself no longer receive fixes.

Read that again with your own store in mind. If you are on Magento 2.4.6 running PHP 8.1, you have had a potential PCI compliance exposure since the start of this year, entirely separate from anything Adobe is doing to your Magento version.

PHP 8.2 reaches end of life on 31 December 2026, and Adobe flags the same risk for 2.4.6 stores running it, advising merchants to plan an upgrade or migration before the end of this year.

Adobe is careful to say that assessing PCI compliance is the merchant's responsibility and recommends consulting your qualified security assessor. That is reasonable, but it also means nobody will tell you about this unless you ask. If you take card payments, this sits alongside the basics of secure payment gateway integration as something to verify rather than assume.

What Adobe never covered, even while you were supported

Related, and equally under-discussed. Adobe's policy states plainly that it does not provide security and quality fixes for third-party services and software dependencies that reach end of life while you are inside your support window. That list includes PHP, MySQL, MariaDB, OpenSearch, Redis, Valkey and RabbitMQ.

Maintaining those is your responsibility, and always was.

Adobe goes further for Cloud customers, noting that running unsupported dependency versions may create a vulnerability it cannot resolve, and that it reserves the right to enforce an upgrade of the affected dependency, or to decommission the instance if an upgrade is not possible, regardless of whether your Commerce version is still supported.

The practical takeaway is that "we are on a supported version" was never the complete safety net merchants assumed. A fully supported Magento install sitting on an end-of-life PHP version is still an exposed store. Outdated dependencies also drag on performance, which feeds directly into the page speed benchmarks a business site needs to hit in 2026.

A note on Adobe's own published dates

Worth knowing if you are planning around these deadlines: Adobe's two documentation pages do not currently agree with each other.

The lifecycle policy page, last updated 20 May 2026, lists the end of standard support for 2.4.7 as 31 May 2027 and for 2.4.8 as 31 May 2028. The released versions page, last updated 13 May 2026, gives 9 April 2027 and 11 April 2028 for the same two lines. The released versions page also still describes the free support extension as applying to versions 2.4.4 and 2.4.5, while the lifecycle policy applies it to 2.4.6 and 2.4.7.

Both pages agree on the one that matters most here: the Magento 2.4.6 end of support date of 11 August 2026.

The lesson is not that Adobe is unreliable. It is that you should not build a plan that depends on a specific week eighteen months out. Give yourself a buffer, and if a date is going to drive a real budget decision, confirm it with your Adobe account team rather than a documentation page. We covered the shape of the current release line when Adobe Commerce 2.4.7 was released, and the pattern has held since.

If you are on 2.4.5, your deadline is 12 August

One day later, and easy to miss. Extended support for the 2.4.5 line ends on 12 August 2026, with a security-only period running to May 2027. The 2.4.4 line passed the same point on 14 April 2026.

So this is not one deadline in August. It is two, in the same week, affecting a large share of the remaining Magento installs.

What to do, depending on where you are

You run Magento Open Source 2.4.6. This is the urgent case, because there is no Magento Open Source extended support to fall back on. You will not receive patches after 11 August. Two weeks is not enough time to upgrade a real store safely, so the honest plan is: apply the latest available patch now, get a scoped upgrade quote this month, and schedule the work for the next available window. Do not let it drift into next year.

You run Adobe Commerce 2.4.6. You have until 30 August 2027 with full patches, and a security-only period after that. Use the time properly. Start the extension compatibility audit now, because that is the part that always takes longer than anyone estimates.

You run Adobe Commerce 2.4.6 on Cloud. As above, plus the 1 June 2028 enforcement date. Plan to be off 2.4.6 well before it rather than testing whether Adobe means it.

You are on 2.4.5 or older. You are already past the point where this is a planning exercise. Treat the upgrade as remedial work.

You are questioning whether to stay on Magento at all. That is a fair question, and the answer depends on catalogue complexity, B2B requirements and how much custom code you are carrying. Our comparison of the main ecommerce platforms, Magento, Shopify and WooCommerce, sets out the trade-offs, and if a move is on the table, our guide to Shopify migration covers what that process involves.

Choosing your Magento 2.4.6 upgrade path

Two sensible targets.

2.4.8 went generally available on 8 April 2025 with standard support to 2028. It is the conservative choice: a mature line with five patch releases behind it, and a direct upgrade from 2.4.6 is supported without stepping through 2.4.7 first. For most merchants this is the sensible Magento 2.4.6 upgrade path.

2.4.9 went generally available on 12 May 2026 with standard support to May 2029, giving you the longest runway. It is a bigger jump. Industry coverage of the release reports that it replaces several core framework components and moves the supported stack forward significantly, which makes it closer to a server rebuild than a code update. Confirm the specific PHP, search and cache requirements against Adobe's system requirements page before committing, and check that your extension vendors have certified compatibility.

Adobe's own recommended long-term path for Cloud customers is different again: migration to Adobe Commerce as a Cloud Service, its managed SaaS platform, where Adobe handles patching and upgrades and the end-of-life cycle does not repeat. That is a commercial and architectural decision rather than an upgrade, and it deserves its own evaluation.

If you want a second opinion on which target fits your store, our Magento development team can scope it against your actual extension list.

How long a Magento upgrade actually takes

A realistic Magento upgrade runs two to six weeks of working time for a typical store. That covers extension and custom code audit, dependency and server preparation, staging build, regression testing and go-live.

Stores with heavy customisation, long extension lists or ERP integrations sit at the upper end and sometimes beyond it. The code change is rarely the hard part. Extension compatibility is what stretches timelines, because you are waiting on other vendors rather than your own team.

If you have not started and you are on Open Source, accept that you will be unpatched for a period, and plan to shorten that period rather than pretending it will not happen.

If you cannot upgrade before 11 August

You can reduce your exposure while you wait.

Apply 2.4.6-p15, the most recent patch for the line, so you enter the deadline as current as the version allows. Confirm what PHP version your server runs and deal with 8.1 as a priority. Tighten admin access with two-factor authentication and IP restrictions, since the admin panel is the most common target on unpatched stores. Put a web application firewall in front of the site. Verify that your backups actually restore, because an untested backup is not a backup.

None of this replaces upgrading. It buys you a safer few months while you do it properly.

Need help planning your upgrade?

The Magento 2.4.6 end of support deadline is not something to work out from a documentation page at the last minute. If you want your version, edition, PHP stack and extension list checked properly before you commit to a date, talk to our team and we will tell you honestly how much time you actually have.

Sources
Adobe Commerce software lifecycle policy, Adobe Experience League, last updated 20 May 2026.
Adobe Commerce released versions, Adobe Experience League, last updated 13 May 2026.
PHP supported versions, php.net.