Skip to main content
nimbryx
All posts
  • Technology
  • Software Development

PHP 8.2 End of Life on 31 December 2026: What to Upgrade To, and in What Order

PHP 8.2 gets no security fixes after 31 December 2026. Support dates for 8.3 to 8.6, which version to pick, and an upgrade order that won't break a live site.

The Nimbryx team

5 min read

Share

PHP 8.2 stops receiving security fixes on 31 December 2026. After that date, the next critical PHP bug will be patched for 8.3 and newer, and an 8.2 server will simply stay exposed. If your WordPress site, Laravel app or old custom PHP system runs on 8.2, the upgrade has to be planned now, not in January.

This is not a hypothetical worry this year. October brought PHP2Shell, and November brought another security release. Here is what the PHP 8.2 end of life means, which version to move to, and the order we would do it in.

PHP support dates, as php.net lists them

Each PHP branch gets two years of active support and then two years of security-only fixes. After that it is end of life. The current table:

  • PHP 8.2: security fixes until 31 December 2026.
  • PHP 8.3: security fixes until 31 December 2027.
  • PHP 8.4: active support until 31 December 2026, security fixes until 31 December 2028.
  • PHP 8.5: active support until 31 December 2027, security fixes until 31 December 2029.
  • PHP 8.6: released on 19 November 2026, supported until 31 December 2030.

PHP 8.1 and older are already end of life. If you are on one of those, everything below applies, only more urgently.

Why this deadline is not theoretical

On 21 October 2026 the PHP project shipped fixes for PHP2Shell, two critical flaws in the engine itself (CVE-2026-109618 and CVE-2026-109619). On 26 October, CISA added both to its Known Exploited Vulnerabilities catalog. 8.2 got a fix that time, in 8.2.35, because it was still inside its security window. We covered the details in PHP2Shell explained.

Then on 19 November the project released 8.5.13, 8.4.28, 8.3.37 and 8.2.36. The advance notice rated the most serious issue critical, while saying it needs non-default or uncommon configurations to be exploitable. Full details were due to be published alongside the releases. Either way, update to the latest release on your branch now.

Start with an inventory

Before choosing a version, find out how many PHP installs you actually have. It is nearly always more than people think. The main website, yes, but also the staging copy, the old campaign microsite on the same hosting account, the server that runs nightly cron jobs, the admin tool a previous developer built, and every Docker image with PHP baked in. Note the version and handler on each (Apache mod_php, PHP-FPM or LiteSpeed) and who is responsible for it. Anything without a name next to it is the one that will still be on 8.2 in March.

An end-of-life runtime doesn't break on the day support ends. It breaks on the day the next bug is found, and by then you are queueing behind everyone else who waited.

Which version to move to

For most business applications we would pick PHP 8.4, or 8.5 if your framework, plugins and hosting already support it. Both give you years of runway.

PHP 8.3 is fine as a stepping stone, but it reaches end of life in December 2027, so going there means repeating this exercise in a year. PHP 8.6 is brand new. Give the libraries you depend on time to declare support before you put it in production.

Check compatibility before you choose. On a Composer project, composer why-not php 8.4lists the packages that block the move. On WordPress, check that your theme and each plugin state support for the target version, and be suspicious of anything that hasn't been updated in two years.

An upgrade order that won't break a live site

  • Copy production to staging on the new PHP version. Same data, same plugins, same config.
  • Turn on deprecation logging and use the site properly: log in, place an order, submit forms, run the reports. Deprecations from 8.2 to 8.4 (implicitly nullable parameter types are one example in 8.4) are warnings now and errors later.
  • Let tools do the boring part. Static analysis such as PHPStan finds type problems, and Rector can apply many version upgrade changes automatically. Review what it changes rather than trusting it blind.
  • Fix, then retest the flows that make money: checkout, enquiry forms, payment callbacks, invoice generation.
  • Switch production at a quiet hour, restart PHP-FPM or Apache so no old workers remain, and confirm the version from a real web request, not just the terminal.
  • Keep the old version available for a quick rollback for a few days.

If you are on shared hosting

Most hosts in India let you pick a PHP version from a dropdown in cPanel. Pick 8.4 or 8.5 on a staging copy first if your plan allows it, or take a full backup before switching the live site. If your host doesn't offer a supported version, that tells you something about how they will handle the next advisory too. Some commercial vendors sell extended support for old branches. It can bridge a gap, but it is a paid delay, not a plan.

Very old custom PHP code is the hard case. Code written for PHP 5 or 7 can need real work to run on 8.4, and occasionally a rebuild is the cheaper route. That is a judgement to make with someone who has read the code, not from the outside.


We upgrade and maintain PHP applications for businesses in Delhi NCR and across India. Our legacy PHP upgrade and migration work covers the move off PHP 8.2 and older, and a PHP security audit tells you what else needs attention while you are in there. If the PHP 8.2 end of life catches you on an app nobody fully understands, send us what you run and we will map out the upgrade.