Owning software · 5 min

PHP 8.2 end of life: what to do before 31 December 2026

PHP 8.2 stops getting security fixes on 31 December 2026. What that means if your business runs on it, which version to move to, and how to plan the update.

Published
Reading time
5 min

Short answer: PHP 8.2 gets its last security fixes on 31 December 2026. Your site won't stop on 1 January, but from then on a hole found in PHP 8.2 stays open. Move to PHP 8.4 or newer if your framework allows it. PHP 8.3 is the shortest step, but it only buys you a year.

What actually changes

Nothing breaks on the day. Your app keeps running on PHP 8.2 exactly as before.

What stops is the patching. When someone finds a security hole in PHP 8.2 after 31 December, the PHP project won't release a fix for it. The newer versions get the fix, and 8.2 doesn't.

The longer you wait, the bigger the move gets. The libraries your app is built on drop old PHP versions in their own time, so staying put means more of them to update at once later.

Where each version stands

From php.net, as of 22 November 2026:

PHP version Security fixes until
8.2 31 December 2026
8.3 31 December 2027
8.4 31 December 2028
8.5 31 December 2029
8.6 31 December 2030

PHP 8.6 came out on 19 November 2026. Check that your framework supports it before you aim for it: Laravel 13, for example, lists PHP 8.3 to 8.5.

Pick the version your framework supports

The PHP version you can move to depends on your framework. For Laravel, from its own support policy:

Laravel Runs on PHP Security fixes until
11 8.2 to 8.4 12 March 2026 (ended)
12 8.2 to 8.5 24 February 2027
13 8.3 to 8.5 17 March 2028

So a Laravel 11 app on PHP 8.2 has two deadlines, and one has already passed. Moving PHP to 8.4 fixes the PHP side and leaves the framework without security fixes. The fix that lasts is Laravel 13 on PHP 8.4 or 8.5. We wrote up what Laravel 11's end of life means separately.

If you're on WordPress, Symfony or plain PHP, the rule is the same: check what your framework, plugins and packages support before you choose.

How to plan the move

  1. Find out what you're running. The PHP version on the server, the framework version, and the libraries the app depends on. If you don't know, we'll check it for free.
  2. Move in small steps, with tests. For a framework, that means one major version at a time, each one tested before the next. Big jumps are where things break quietly.
  3. Keep a way back. A backup you've restored at least once, and the old version ready to switch back to if something goes wrong.
  4. Update the server too. The new PHP runs on the server, so the server's own software usually moves with it.

We do this on our own products first. SportPoint, the platform Daniel co-founded, has run Laravel 13 in production since 28 October 2026, with releases that cause no downtime.

Where we fit

With Security and updates, we move a PHP, Laravel or Node application onto supported versions in one or two weeks, tested, with a way back if anything goes wrong. It starts with the free version check. It isn't a penetration test, and it isn't a guarantee.

Sources: PHP's supported versions and Laravel's support policy, as of 22 November 2026.

Already have software?

A written verdict in 3 to 5 working days, from €1,800: keep, fix or rebuild, and what to do first. Credited if we carry on together within 60 days.