Magento 2.4.9 shipped supporting PHP 8.5 faster than any release in the platform's history. Here's what's actually supported, and why PHP 8.2 being dropped is the detail most merchants should act on.

Here's a quiet but notable detail buried in Magento 2.4.9's general availability release: it shipped supporting PHP 8.5 about six months after PHP 8.5 itself reached general availability. That's not literally "day one," but it's worth knowing Magento's history here: the platform has historically lagged a full major PHP release behind, often taking the better part of a year (sometimes longer) to officially support a PHP version the rest of the ecosystem had already moved on to. Six months is the shortest gap Magento has managed yet.
Magento 2.4.9 supports PHP 8.4 and 8.5, with 8.5 positioned as the recommended production target. Both PHP 8.2 and PHP 8.3 support are dropped entirely: if you're still running 8.2 or 8.3, upgrading to 2.4.9 means moving your PHP version at the same time; the two moves have to happen together.
PHP 8.5 itself shipped on 20 November 2025, with active support running until 31 December 2027 and security fixes continuing until 31 December 2029, which makes it, practically speaking, the longest-runway PHP version a Magento store could realistically target right now.
In past cycles, the gap between a new PHP release and Magento officially supporting it created a real planning headache: merchants either stayed on an older, increasingly unsupported PHP version waiting for Magento to catch up, or ran an unofficial configuration and hoped nothing broke. Narrowing that gap to a matter of months, rather than the better part of a year, removes a lot of the "wait and see" decision-making from a Magento upgrade roadmap. It's a small operational win that compounds: hosting providers can standardise sooner, security patches land without as long a compatibility question mark attached, and agencies like ours can recommend a PHP version with more confidence and less caveat than in previous cycles.
Here's the detail with a real deadline attached, separate from anything to do with 2.4.9 specifically: PHP 8.2 reaches its own end of life on 31 December 2026, meaning no further security patches from the PHP project after that date, Magento upgrade or not. We've written the full breakdown of what that means, and the Magento-version-to-PHP-version compatibility table to go with it, in PHP 8.2's end of life and what it means for your Magento store. If you're on an older Magento release and haven't scheduled a PHP upgrade yet, that post is the one to read next; it matters whether or not you're moving to 2.4.9 this year.
It's also worth a brief mention of PHP's own patch cadence while we're on the topic: on 21 October 2026, the PHP project shipped fixes for the "PHP2Shell" vulnerabilities (CVE-2026-109618 and CVE-2026-109619) across PHP 8.2.35, 8.3.36, 8.4.27 and 8.5.12. Whichever supported PHP version you're running, "on a currently supported branch" still needs pairing with "actually patched to the latest point release": the two aren't the same thing.
If you're planning a 2.4.9 upgrade from scratch, target PHP 8.5 directly rather than treating 8.4 as a permanent home: the longer support runway makes it the more future-proof choice, and 2.4.9 supports it from its own release with no compatibility reason to hold back. If you're migrating from an older Magento release still on PHP 8.1, 8.2 or 8.3, budget the PHP upgrade as part of the same project rather than a separate step; trying to sequence them independently tends to create more testing cycles, not fewer.
If you'd like a second opinion on which PHP version makes sense for your specific hosting setup and upgrade timeline, talk to Deploy: we plan the infrastructure side of a Magento upgrade alongside the application side, precisely so these two pieces don't end up fighting each other on your roadmap.
Sources: Adobe's own 2.4.9 release notes, HeroDevs' PHP end-of-life timeline, endoflife.ai's PHP version tracker.
Last updated 14 May 2026.