Back to Blog Homepage
    Deploy Blog
    Nathan Chick

    Magento 2.4.5 and 2.4.6 Support Has Ended - Here's What Changes and What to Do

    Standard support for Magento 2.4.5 and 2.4.6 both ended by 11 August 2026. If you're still on either version, here's exactly what you've lost and your realistic upgrade paths.

    Magento 2.4.5 and 2.4.6 Support Has Ended - Here's What Changes and What to Do

    Magento 2.4.5's extended support and 2.4.6's standard support both ended on 11 August 2026. If you're running either version, nothing broke overnight, but what you're entitled to from Adobe has changed significantly, and it changed on the same day APSB26-92 landed, this year's reminder that Magento's patch calendar hasn't been getting any quieter.

    What "end of support" actually means, version by version

    Adobe uses three distinct terms here, and the difference between them matters more than it sounds like it should:

    Version Standard support ended Extended support ends (Adobe Commerce) Security-only fixes until (Adobe Commerce)
    2.4.5 12 August 2025 11 August 2026 31 May 2027
    2.4.6 11 August 2026 31 August 2027 31 May 2028

    Standard support is the full package: new features, non-security bug fixes, and security patches. Extended support narrows that down but still includes some non-critical fixes. Security-only is exactly what it says: you'll keep getting fixes for genuinely critical vulnerabilities, nothing else, and historically those fixes arrive later than the equivalent patch for currently-supported versions, since they have to be separately backported.

    The extended and security-only columns above are an Adobe Commerce benefit specifically: Magento Open Source doesn't get an extended or security-only phase at all, so an Open Source store on either version is already past all official support the moment its standard-support date passes. If you're running Adobe Commerce on 2.4.5, you do still have a security-only window open until 31 May 2027, but it's critical-fixes-only, it's the last extension you'll get, and historically these backports lag well behind the fix for a currently-supported version.

    Why this matters more in 2026 than it would have a couple of years ago

    This deadline doesn't exist in a vacuum. 2026 has been an unusually heavy year for Magento and Adobe Commerce vulnerabilities: PolyShell in July, APSB26-92 in August, StyleSmuggler and APSB26-138 in September, and October's APSB26-153. We've pulled the whole pattern together in our full-year review of 2026's Magento zero-days. Both APSB26-92 and the StyleSmuggler hotfix explicitly listed Adobe Commerce 2.4.4 through 2.4.9 (which covers 2.4.5) and Magento Open Source 2.4.6 through 2.4.9 among the affected versions, and PolyShell's unrestricted file-upload flaw affected every production release up to and including 2.4.8, which covers both versions too.

    That's the concrete, not-abstract version of what this deadline means: this year alone has produced several critical, unauthenticated vulnerabilities that directly hit 2.4.5 and 2.4.6, and the safety margin for getting a fix only shrinks from here. An Open Source store on either version already has no official route to a fix for anything newly discovered. An Adobe Commerce store on 2.4.5 is relying on its last security-only window, with no further extension once that closes in May 2027.

    Your upgrade paths

    • From 2.4.5 or 2.4.6 to 2.4.8: the smaller jump, if you need to buy time with a less disruptive project while you plan something bigger.
    • Straight to 2.4.9: a larger jump (it swaps Zend Cache for Symfony Cache, TinyMCE for HugeRTE, and changes PHP and database requirements all at once), but it means you're not planning a second upgrade again shortly afterwards. Worth reading what 2.4.9 actually changes under the hood before deciding, since the scope of testing differs meaningfully between the two paths.

    Either way, factor in the PHP 8.2 end-of-life deadline at the same time. If you're moving off 2.4.5/2.4.6, you're very likely moving your PHP version too, and it's a much cleaner project done once rather than twice.

    FAQ

    Is my store still PCI compliant if I'm on an unsupported Magento version? Running unsupported software with known, unpatched vulnerabilities is exactly the kind of thing a Qualified Security Assessor will flag, and it works against you in the event of a breach investigation. See our broader piece on who's responsible for PCI compliance for how that plays out in practice.

    What's the difference between security-only fixes and full support? Security-only means critical vulnerability fixes alone, typically arriving later than the equivalent fix for a currently-supported version. Full support includes new features and non-security bug fixes too.

    Should I upgrade straight to 2.4.9 or go via 2.4.8 first? It depends on how much custom code and how many third-party extensions you're carrying. A smaller, highly customised store sometimes benefits from the smaller 2.4.8 step first; a leaner store is often better off absorbing the bigger 2.4.9 jump in one project. Worth a proper assessment rather than a default answer either way.

    If you'd like that assessment, Deploy's upgrade team plans exactly this kind of decision for a living, including sequencing it against PHP and database deadlines you're likely facing at the same time.

    Sources: Uncap's Magento end-of-life guide, Shakewell's Magento 2.4 end-of-life dates.

    Last updated 13 August 2026.

    Need Help with Your eCommerce Project?

    Get expert advice from our Magento specialists and marketing professionals.