PHP 8.2 loses all security support at the end of 2026, and Magento 2.4.9 has already dropped it entirely. If your store is still on it, here's the real deadline and your upgrade paths.

PHP 8.2 reaches end of life on 31 December 2026. From 1 January 2027, the PHP project stops fixing security flaws in that branch altogether, including critical ones. Your Magento store won't fall over the moment the clock ticks past midnight. But from that date, every new PHP vulnerability discovered against 8.2 becomes a permanent, unpatched hole in your stack, with no official fix ever coming. And if you're planning to move to Magento 2.4.9, you can't bring PHP 8.2 with you anyway: Adobe dropped support for it entirely in that release.
It doesn't mean PHP 8.2 stops running. Your server keeps executing exactly the same code it did the day before. What stops is the safety net: no more security patches, from anyone upstream. Any vulnerability discovered after the cutoff sits there indefinitely, and it becomes the kind of gap attackers specifically go looking for, because they know a huge number of sites running the affected version will never get fixed. Hosting providers increasingly refuse to support EOL PHP versions on current plans, and if you're ever assessed for PCI compliance, running unsupported software with known, unpatched vulnerabilities is not a position you want to explain to a Qualified Security Assessor.
Compatibility has shifted release by release, and it's easy to lose track if you've been on the same version for a while:
| Magento version | Supported PHP versions |
|---|---|
| 2.4.6 | 8.1 – 8.2 |
| 2.4.7 | 8.2 – 8.3 |
| 2.4.8 | 8.3 – 8.4 |
| 2.4.9 | 8.3 – 8.5 (8.2 dropped entirely) |
Treat this table as a starting point rather than gospel: always check Adobe's own system requirements page for your exact version before planning an upgrade, since minor compatibility details do get refined between releases.
The practical knot this creates: if you're on 2.4.6 or 2.4.7 today, you're likely already running PHP 8.2, and that's currently fine on either version. But it won't be safe to keep running much longer, and it stops being an option at all the moment you move to 2.4.9. That means your PHP upgrade and your Magento upgrade are really one project, not two separate ones you can schedule independently.
If you're still on Magento 2.4.6, this deadline doesn't arrive in isolation. That version's standard support already ended in August 2026, leaving it on security-only fixes until May 2028. Combine that with PHP 8.2 going dark at the end of this year, and you've got two separate clocks running out in the same few months, which is exactly the kind of situation that turns into an emergency project instead of a planned one if you leave it too late.
Will my store stop working on 1 January 2027 if I'm still on PHP 8.2? No, it'll keep running exactly as it did the day before. What changes is that any new vulnerability found in PHP 8.2 from that date on will never be patched, which is a risk that compounds the longer you stay on it.
Can I upgrade PHP without upgrading Magento? Yes, within the ranges in the table above. Moving from 8.2 to 8.3 is possible on 2.4.7 without touching your Magento version, and 2.4.8 already supports 8.3/8.4. It's a smaller project, but it only buys you a limited amount of time before the Magento upgrade becomes unavoidable too.
What's the safest PHP version to target for long-term support? PHP 8.4 has security support until the end of 2028, and 8.5 until the end of 2029. Either is a sensible target if you're planning not to touch this again for a while, provided your Magento version supports it.
If you want help sequencing a combined PHP and Magento upgrade rather than firefighting two deadlines separately, that's exactly the kind of project our upgrade team plans for a living.
Sources: HeroDevs' PHP end-of-life timeline, endoflife.ai's PHP EOL dates.
Last updated 10 November 2026.