Quick answer: Adobe ended standard support for Magento (Adobe Commerce) 2.4.6 on 11 August 2026, and 2.4.5 has been out of standard support since August 2025. Stores on these versions no longer get regular security and quality patches, which raises the risk of breaches, failed PCI compliance audits and extension problems. If you’re on 2.4.5 or 2.4.6, plan your upgrade to 2.4.8 or 2.4.9 now. Don’t wait for the next incident.
What “end of support” actually means
When a Magento version reaches end of support, Adobe stops releasing regular security patches, bug fixes and quality updates for that release line. The store doesn’t switch off. It keeps trading, but every new vulnerability discovered from here on is one you may not be able to patch officially.
This matters more than usual right now. Adobe confirmed active exploitation of a critical zero-day (CVE-2026-75650) in September. We covered it in our urgent guide for Australian merchants. Stores on supported versions could apply the hotfix. Stores on unsupported versions were left to patch by hand or go without.
Are you affected? How to check your Magento version
- Log in to the Magento Admin panel and scroll to the footer, where the version number is shown.
- Or run bin/magento –version from the command line.
- Or check composer.json for the magento/product-community-edition or magento/product-enterprise-edition version.
If it starts with 2.4.5 or 2.4.6 (or anything older), keep reading.
The real risks of staying on an unsupported version
1. Security exposure. New vulnerabilities in the core platform become permanent for your version. Attackers target outdated Magento stores because the flaws are public and the fixes aren’t available.
2. PCI DSS compliance. If you take card payments, you’re expected to run supported software with current security patches. An unsupported platform can cause problems in a PCI assessment or a request from your payment provider. Adobe has also flagged that compliance is at risk for merchants who don’t upgrade by the end of 2026.
3. The PHP clock is separate. Your Magento version depends on a PHP version, and PHP versions have their own end-of-life dates. A store can be covered by extended Magento support and still run on PHP that no longer gets security fixes. Check both.
4. Australian privacy obligations. If a breach exposes customer data, you may have to notify affected people and the OAIC under the Notifiable Data Breaches scheme. Running unpatched software makes that outcome more likely and harder to defend.
5. Extension and integration drift. Extension vendors, payment gateways, shipping providers (including Australian carriers) and search tools move to current Magento versions. The longer you wait, the more likely it is that an extension update will no longer support your old version.
6. A growing upgrade bill. The gap between your version and the current one widens each month. Delaying doesn’t make the upgrade cheaper. It makes it bigger.
Your options
| Option | Best for | Trade-off |
|---|---|---|
|
Upgrade to 2.4.8 or 2.4.9 |
Most merchants |
Needs testing of extensions and custom code |
|
Adobe Commerce extended support (licensed stores) |
Short-term breathing room |
Temporary, security-focused, and it doesn’t fix PHP or third-party end-of-life |
|
Adobe Commerce as a Cloud Service |
Brands that want less infrastructure to manage |
Different cost model and a migration project |
|
Replatform |
Stores with little customisation and rising running costs |
Higher short-term cost and SEO risk if not planned well |
For most Australian stores, upgrading is the most practical path. Magento 2.4.9 reached general availability in May 2026, so the newest release is now mature enough to consider, depending on your extension compatibility. Version 2.4.8 is a lower-risk target if your extensions haven’t caught up yet.
Upgrade checklist
- Back up everything: database, media and codebase.
- Build a staging copy of your live store. Never upgrade production first.
- Audit your extensions. List every third-party module, check which have versions for your target release, and flag any that are abandoned.
- Review custom code for deprecated functions and compatibility issues.
- Check the stack: PHP, MySQL or MariaDB, OpenSearch, Redis, Varnish and Composer versions.
- Run the upgrade on staging and fix errors.
- Test the revenue-critical paths: product pages, search, cart, checkout, payment gateways, shipping rates, GST, emails and admin order handling.
- Test performance. Compare speed before and after. If pages feel slow, see our guide to speeding up Magento.
- Plan the go-live for a low-traffic window, with a rollback plan.
- Monitor closely for 1–2 weeks after launch.
How long does an upgrade take, and what does it cost?
It depends on how many extensions and how much custom code you have.
- Simple store (few extensions, mostly standard features): typically a few weeks.
- Mid-complexity store (a dozen or more extensions, some custom code): several weeks.
- Heavily customised store: can run to two months or more.
[Add your own pricing here, for example “Upgrades from AUD $X” or “Contact us for a fixed-price audit.”]
Why an upgrade is also the right time to set up ongoing support
Many stores fall behind because nobody owns the job. An upgrade isn’t a one-off event. Adobe releases security patches regularly, and critical issues can appear with little warning.
An ongoing support plan covers monthly patching, monitoring, backups, fast response when something breaks, and a roadmap for the next upgrade. If you’re unsure how that differs from routine upkeep, read Magento Support vs Magento Maintenance. For the Australian view of what a good plan includes, see Magento Support Australia: What Every Online Store Needs to Know.
Not sure where your store stands?
We’ll check your Magento version, PHP and server stack, extensions and security patch level, and give you a clear upgrade plan.
Book a free Magento version and security check →
Or explore our Magento upgrade service and Magento maintenance plans.
FAQ
When did Magento 2.4.6 support end?
Standard support for the 2.4.6 release line ended on 11 August 2026.
Is Magento 2.4.5 still supported?
No. Standard support ended in August 2025, and the extended support window for licensed Adobe Commerce stores has now closed too.
Will my store stop working on an unsupported version?
No, it will keep running. The risk is that new vulnerabilities won’t be patched officially, and compatibility problems build up over time.
Can I stay on 2.4.6 with Adobe Commerce extended support?
If you have a licensed Adobe Commerce plan, extended support applies. It’s a temporary bridge, and it doesn’t solve third-party end-of-life issues such as PHP.
Which version should I upgrade to?
Most stores should target 2.4.8 or 2.4.9, depending on extension compatibility. A technical audit will tell you which is safer for your store.
Is an unsupported Magento store a PCI compliance problem?
It can be. PCI DSS expects supported software with current security patches. Confirm your requirements with your payment provider or QSA.
How much does a Magento upgrade cost in Australia?
It depends on your extensions, custom code and number of versions to jump. A short audit is the quickest way to get an accurate quote.