← Back to blog

Guides

Magento 2.4.8 Is Here: PHP 8.4, 497 Fixes, and PHP 8.1 on the Clock

April 10, 2025 - by Alexandru-Manuel Carabus

Magento 2.4.8 shipped on April 8, 2025 with PHP 8.4 support and 497 fixes. Here is what actually changes, what tends to break, and why PHP 8.1 stores are now on a deadline.

A navy core module being upgraded: a dim grey component drifts away while a glowing blue component with an orange accent chip clicks into place, illustrating a version upgrade and a retired runtime.

Adobe released Magento Open Source 2.4.8 on April 8, 2025. It is a large release: 497 bug fixes, new platform support and a meaningful shift in PHP requirements. If you own a Magento store, two things matter here, what you gain and what you are now on a clock to fix.

What is new in 2.4.8

The headline is PHP 8.4 support, with PHP 8.3 as the new minimum and PHP 8.1 support removed entirely. The release also moves to MariaDB 11.4 and MySQL 8.4, upgrades TinyMCE from 5 to 7.3, adds the newer Google Maps API, and brings GraphQL and API scalability improvements. On top of that sit the 497 core bug fixes and the usual batch of security hardening.

What actually breaks on the way to PHP 8.4

PHP 8.4 removes and changes functions, methods and interfaces that older code relied on. In practice, the work is in your extensions and custom modules, not the core. Anything not yet updated for 8.4 can throw fatal errors or silent warnings, so the upgrade is a code-review job before it is a deployment job. This is exactly the kind of pass LIQUIDLAB AI aids, scanning a codebase for deprecated calls before they reach production.

PHP 8.1 is the real deadline

PHP 8.1 reaches end of life on December 31, 2025. Stores on Magento 2.4.4 through 2.4.6 run on PHP 8.1, which means that after that date they sit on an unsupported language runtime. In a cardholder data environment that is a PCI DSS problem, not just a technical one. An unpatched runtime in the payment path can raise your acquiring fees, trigger remediation demands, and make any breach far more expensive.

Should you jump to 2.4.8 now?

If you are on 2.4.6 or earlier, plan the upgrade this year so you land on a supported PHP release before the 8.1 cutoff. If you are already on 2.4.7, the pressure is lower, but 2.4.8 is where the current security and platform work lives, so it belongs on your roadmap. Either way, the sooner you test against PHP 8.4 in staging, the fewer surprises you inherit.

How we approach a 2.4.8 upgrade

The reliable path is boring on purpose: a staging clone, a full extension and custom-code audit against PHP 8.4, a regression pass on checkout and search, then a scheduled cutover. If you want a second set of eyes on your upgrade plan or your PHP timeline, book a free strategy call with LIQUIDLAB.