Magento's August 2026 support cliff is here: version 2.4.6 reaches end of standard support on August 11, 2026, and 2.4.5 loses its last safety net a day later. If you run a Magento Open Source or Mage-OS store, this is not a soft deadline. Open Source has no extended support tier, so once standard support closes the patches simply stop. For a premium storefront, that turns an upgrade you keep deferring into a security and compliance problem with a fixed date on it.
What actually ends on August 11, 2026
Magento and Adobe Commerce 2.4.6 reach end of standard support on August 11, 2026, and 2.4.5 reaches end of extended support on August 12, 2026. Adobe's own lifecycle table is the record here, and it is sharper than the round "everything dies on the 11th" framing going around. 2.4.5 standard support already ended in August 2025, 2.4.4 extended support ended on April 14, 2026, and 2.4.6 standard support is the line that lands this week, per the Adobe Commerce lifecycle policy. Once a version's support window closes, Adobe stops shipping fixes for it. A vulnerability found in core after that date becomes a permanent exposure on your store unless you have already moved to a supported line.
Adobe Commerce vs Magento Open Source: who really loses cover
Adobe Commerce buys a cushion that Magento Open Source does not get at all. Adobe reserves the extended-support tier for paying Adobe Commerce customers, and leaves the Magento Open Source edition out of it entirely, per Adobe's lifecycle policy FAQ. That single distinction reshapes the deadline depending on which edition you run. An Adobe Commerce store on 2.4.6 slides into extended support through August 30, 2027, then a security-only period after that, so it keeps receiving critical fixes through the Quality Patches Tool. A Magento Open Source or Mage-OS store on 2.4.6 gets nothing after August 11, 2026. For Open Source, end of standard support is the real end of patches, with no grace period. This lands hardest on exactly the stores a performance-led studio tends to run, because Hyvä storefronts often sit on Open Source or Mage-OS rather than paid Adobe Commerce. If that describes you, the August date is not advisory. It is the day your core stops receiving security fixes.
2.4.8 vs 2.4.9: which version to upgrade to
Upgrade to 2.4.9 if you can absorb the framework jump, and to 2.4.8 only if you need a shorter hop with more runway than 2.4.6 offers. Adobe's lifecycle table puts 2.4.8 standard support through May 31, 2028 and 2.4.9 through May 31, 2029, so 2.4.9 buys a full extra year of cover. 2.4.9 is also the larger technical move. It reached general availability in May 2026 with PHP 8.5 and 8.4 as the supported runtimes and PHP 8.2 removed outright, and it counts 666 fixes in the Commerce core and 580 in Open Source, alongside the removal of Laminas MVC, Zend_Cache and TinyMCE. We covered why that release is unusually disruptive in our note on the 2.4.9 framework jump. The practical read: if your modules are already clean on PHP 8.3 and above, go straight to 2.4.9 and take the full window. If you are jumping off 2.4.5 or 2.4.6 with heavy legacy modules that still touch Laminas, 2.4.8 is a defensible intermediate step, but treat it as a stopover, not a destination, since its window closes in 2028.
What we would change this quarter
Confirm your exact version and edition today, then book the upgrade before the patch gap opens rather than after it. Three concrete moves follow. First, check whether you are on Adobe Commerce or Magento Open Source, because the same 2.4.6 store faces either a 2027 cushion or a hard August 11 stop depending on the answer, and most teams do not have that distinction written down anywhere. Second, if you are on Open Source 2.4.5 or 2.4.6, scope a jump to 2.4.9 now, because Adobe moved to a monthly isolated security-patch cadence in 2026 and an unsupported core simply drops out of it, leaving PCI compliance and every future CVE on your side of the fence. Third, fold the frontend into the same window, since an upgrade quarter is the cheapest time to move off a legacy Luma theme. That is why we pair version upgrades with Hyvä work on our Magento and Hyvä builds and lay the sequence out in our Hyvä migration guide. Deferring is the expensive option. A store that skips this window is not saving money, it is booking a larger emergency migration later, on top of a live security exposure in the meantime.