Magento Long-Term Support: Keep 2.4.6 Patched While You Plan
Ask AI about this article
What does Magento long-term support look like once Adobe stops patching your version? A merchant we look after asked us a version of that this fall. Their store runs Magento Open Source 2.4.6, which lost Adobe's support on August 11, 2026. They knew an upgrade was coming. They also had a new ERP integration on the calendar. And they had open questions about which custom features they would even keep. So: do we need to upgrade now? What are our options?
Our answer was no, not yet. We can keep your current version patched for a while, so you can plan the upgrade properly instead of rushing it.
If you want the background on what actually ended in August, we covered it in what happens to your Magento store after end of support. This post is the practical follow-up: what you can do about it. Stay patched on the version you run, know where that stops working, and plan the upgrade on your own timeline. It applies whether you run Adobe Commerce, Magento Open Source or a Mage-OS build. We will point out where the editions differ.
Does Magento have long-term support for older versions?
Not from Adobe, not really. Here is where things stand, from Adobe's lifecycle policy:
- Adobe Commerce 2.4.6: standard support ended August 11, 2026. Paying customers get extended support until August 31, 2027, then security-only fixes until May 31, 2028.
- Adobe Commerce 2.4.4 and 2.4.5: security-only fixes until May 31, 2027.
- Magento Open Source 2.4.6: nothing official. Adobe's notes for its October 2026 security update say it plainly: "Open Source merchants can only download patches for version 2.4.7 or later."
Adobe is also clear that the security-only window is not a place to settle in. In its own words: "Treat the security-only period as migration time, not as a long-term support tier."
So if long-term support means someone at Adobe keeps fixing your old version for years, that does not exist. What does exist is backporting.
Why can't I download Adobe's security patch for 2.4.6?
Say you run Magento Open Source 2.4.6 and try to download a recent 2.4.6 patch with your Marketplace keys. You will likely see something like "Access denied. Your account does not have the required entitlement for this patch."
Nothing is wrong with your keys. Adobe still builds 2.4.6 patch files for Adobe Commerce customers on extended support. Open Source accounts only get the 2.4.7 and newer files.
So the fix exists. It is written for the next version up, and that code is very close to yours. That gap is exactly what backporting fills.
What does backporting a Magento security patch mean?
A security patch is a small set of code changes that closes a specific hole. Adobe writes each month's fixes for the versions it still supports. Most of the code those fixes touch has barely changed between 2.4.6 and 2.4.7.
Backporting means taking the fix Adobe wrote for the newer version and carrying it back to yours:
- Apply Adobe's patch for the next version up to your older code.
- Most of it lands cleanly. Port the parts that don't by hand, so they do the same job in your version's code.
- Rebuild the patch file so it applies to your exact version with no guesswork.
- Check every vulnerability in Adobe's bulletin against the patch, so you know which ones it covers and which don't apply to your store.
- Test it on staging, then ship it.
Here is what that looked like on the 2.4.6 store from the start of this post. Adobe's July and August 2026 fixes still came in 2.4.6 versions we could use directly. September and October did not, so we backported both from Adobe's 2.4.7 files.
October mattered most. Its headline flaw, CVE-2026-103849, let an attacker run code on the server without logging in. Adobe scored it 10.0 out of 10. Our backport reached production less than two weeks after Adobe published the bulletin.
Most of the changes applied as they were. A handful needed rewriting, because 2.4.7 had picked up a few pieces of code that 2.4.6 never got. That is normal. It is also an early warning sign, and we will come back to it.
How do you keep a backported patch from disappearing?
This is the part that bites people. Magento's core code lives in the vendor/ folder. Composer rebuilds that folder on every install, and most projects keep it out of git. So a patch someone applied by hand on the server quietly vanishes at the next deploy. Nothing in git shows it was ever there.
We keep every security patch in the project's own repository. A script re-applies them after each composer install:
"scripts": {
"post-install-cmd": ["bash m2-hotfixes/apply.sh"],
"post-update-cmd": ["bash m2-hotfixes/apply.sh"]
}
The script skips patches that are already in place, and it stops the deploy cold if a patch will not apply. A failed deploy is annoying. A deploy that quietly ships an unpatched store is much worse.
It also gives you a paper trail. That folder and its history show which of Adobe's bulletins your store covers and when each fix went in. You want that ready when your payment processor, your insurer or your own leadership asks "are we patched?"
Don't go by the version number, either. Adobe now ships these monthly fixes as separate patch files, not new Composer versions. A store missing three months of them can report the same version as one that has them all. If you are not sure what your store really has, that is the first thing an Adobe Commerce security audit checks.
What if Adobe never ships a patch for your version?
Sometimes a fix reaches the newest release first and older lines later. PolyShell, a file-upload flaw disclosed in March 2026, is a good example. Sansec reports that Adobe's fix shipped in 2.4.9 in May and only reached older supported lines in July. For a line Adobe no longer supports, "later" never comes.
That is why long-term support for an older version is really a promise about people. Someone has to read every bulletin, decide what applies to your store, and do the work in your exact code. That is true on Adobe Commerce, on Magento Open Source and on a Mage-OS build alike. So ask whoever supports your store how they handle a fix that only ships for newer versions.
What is the difference between a patch and an upgrade?
We hear this one a lot, often as "is this an upgrade or an update?" It's a fair question. The two cost very different amounts.
A patch changes a handful of files to close one or more holes. The store stays on the same version. It is small work you can test quickly.
An upgrade moves the whole store to a new release line. Going from 2.4.6 to 2.4.8 means a newer PHP (8.3 or 8.4 instead of 8.2). It usually means newer database and search versions too. Then every extension gets updated and every integration gets tested again. The version bump itself is not the expensive part. Everything your store is connected to is.
Backporting lets you keep doing the small thing while you plan the big one.
What can't backporting fix?
Backporting is a bridge, not a place to live. Be honest with yourself about four things.
It gets harder every month. Each new Adobe fix is written against code that has moved further from yours. One day a fix will depend on something your version simply does not have. When most of a patch needs rewriting instead of applying, the bridge is getting short.
It doesn't patch PHP. Magento 2.4.6 runs on PHP 8.1 or 8.2. PHP 8.1 stopped getting security fixes at the end of 2025, and PHP 8.2 stops on December 31, 2026. Adobe's lifecycle page flags PHP 8.2 as a PCI compliance risk from the end of 2026. Backporting Magento's fixes does nothing for the language underneath it. Some Linux distributions keep patching the PHP they ship for longer. So ask your host what you actually run and who patches it. If nobody can answer that, your planning window is shorter than you think.
It doesn't fix your extensions. Your payment, tax and shipping modules, and the connector to your ERP, have their own vendors and their own bugs. Those vendors test on current versions. Sooner or later, the fix you need for a module will only ship in a release that needs a newer Magento. Keep extension licenses current too. An expired license can block a module update and a dry-run upgrade at the same time.
It doesn't settle PCI on its own. PCI DSS v4.0.1 asks you to install patches for critical vulnerabilities within one month of release (Requirement 6.3.3). Picture a backported fix that goes live inside that window, with a record of what it covers. That is a far better answer than "there is no patch for our version." Whether it is enough is up to your assessor or your payment processor. Ask them before you need the answer.
When is it time to upgrade Magento?
When any of these is true, stop extending the bridge and put the upgrade on the calendar:
- Your PHP version is out of security support and your host can't keep it patched. For 2.4.6 on PHP 8.2, that clock runs out on December 31, 2026.
- Backports need more rewriting than applying. That is the code telling you it has drifted too far.
- A module or integration you depend on drops your version: the payment gateway, the tax service, the ERP connector.
- Your payment processor or PCI assessor won't accept a backported platform.
- You are on Adobe Commerce and your line's security-only window is closing. That is May 31, 2027 for 2.4.4 and 2.4.5, and May 31, 2028 for 2.4.6.
- The business has finally decided what the store needs to do. That one is a good reason, not a bad one.
You can look up your own version's dates in our Adobe Commerce end-of-life checker.
How do you plan a Magento upgrade around an ERP change?
Back to the merchant from the start. Their real worry was not the version number. It was timing. A new ERP integration was coming, and they did not want the upgrade landing on top of it. A lot of their custom code also served one sales program whose future the business had not decided yet. Upgrading before that decision meant paying to carry code they might throw away.
So we suggested an order:
- Keep the store patched now. Backport each month's fixes, so security is not what sets the schedule.
- Finish the ERP integration first. Once orders, prices and stock flow between the store and the new ERP, you know exactly what the upgraded store has to do. The working integration becomes the test the upgrade has to pass.
- Make the business decisions. Which custom features stay and which go. Every feature you drop is one you don't pay to upgrade.
- Then upgrade, in a quiet window. Not during your busy season, and not in the same quarter as an ERP change.
Step two is the one people skip. Do the upgrade and the ERP change together, and when an order fails to sync, you can't tell which change broke it. One at a time, and each change has a clear "before" to compare against. Knowing they had time to do it in that order was a relief.
A few things make the eventual upgrade smaller:
- Write down everything that is customized and everything that is integrated. That list is your upgrade estimate.
- Ask each integration vendor which versions they support. Maybe you run Epicor Prophet 21, NetSuite or Dynamics behind your store. Ask the connector vendor before you pick the target version, not after.
- Renew extension licenses before the dry run, not during it.
- Do a dry-run upgrade on staging early, just to see what breaks. It is cheap information.
- Plan real end-to-end tests: place orders and watch them reach the ERP, check customer pricing, run a refund.
Our ERP integration readiness checklist goes deeper on the integration side. And whatever date you pick, keep it clear of your busiest weeks. We wrote about what breaks between your ERP and your storefront at peak for exactly that reason.
What should you ask whoever supports your store?
If you are on an older version and not ready to upgrade, these five questions tell you whether you are really covered:
- Which Adobe security bulletins do you track for us, and how do you decide what applies?
- When Adobe doesn't ship a patch for our exact version, do you backport it or tell us to upgrade?
- How fast does a critical fix reach production?
- Where is the record of which fixes our store has? Not the version number, the patches themselves.
- When will you tell us backporting has stopped being safe?
The last one matters most. A good partner tells you the bridge is running out well before it does. That is how we run support for Adobe Commerce stores. We keep you patched on the version you are on, and we tell you honestly when it is time to move.
Here's a small thing you could do this week. Ask whoever runs your store to show you Adobe's September and October 2026 fixes in your code. If they can, wonderful, you are in good hands. If they can't, that is worth a conversation, and we are happy to have it with you.