Don’t forget PHP 8.2 goes unsupported on 31 December

On 31 December 2026, PHP 8.2 stops receiving security fixes. After that date, any vulnerability found in the runtime your application sits on will not be patched — your code keeps running, it just stops being defended.

Who this is for

  • Anyone running a PHP application in production — Laravel, Symfony, WordPress, or bespoke — without knowing the exact runtime version.
  • Engineering leads who inherited an estate and have never audited what each service actually runs on.
  • CTOs and platform owners who need to book the upgrade into a sprint before the year-end change freeze, not during it.

What’s happening

This is a diary entry, not a crisis. PHP publishes its support windows years ahead, and this one has been on the calendar since 8.2 shipped in December 2022. Active support already ended on 31 December 2024; security-only support runs out on 31 December 2026. The trap is that nothing breaks on 1 January. The site loads, the cron jobs fire, the invoices go out. The only thing that changes is that you are now running production on an undefended runtime, and you will not notice until a CVE lands and there is no patch coming.

I have walked into more than one estate where the answer to "what PHP version are we on?" was a shrug and a guess. The version is set in a Dockerfile nobody has opened in eighteen months, or baked into a managed platform image, or spread across three servers that were provisioned at different times. Finding out is the first job, and it is usually the one people skip.

Free · 4 minutes

Do you actually know what you are running — and what it is about to cost you?

Fourteen questions on the systems you depend on, the ones nobody owns, and the support dates that turn a routine upgrade into a forced re-platform. Banded finding on screen, full sheet by email.

Why it bites

The date bites harder than it looks because your framework has its own floor. Laravel, Symfony, WordPress and the rest each declare a minimum PHP version, and the newer releases have already moved past 8.2. So the upgrade is rarely "bump the runtime and redeploy." It is a chain: PHP 8.3 or 8.4 pulls a framework upgrade, which pulls dependency upgrades, which surface the deprecations you have been ignoring since 8.1. Each link is small. The chain is not. If you start it in December you are doing it under a deadline you set yourself for no reason.

An unsupported runtime is also the kind of thing that shows up in a due-diligence review or a security questionnaire and costs you nothing until, suddenly, it costs you the deal. If you build products, the obligation to keep shipping fixes across a support period is now written into law — I covered what that forces you to build in the CRA vulnerability-handling piece. A runtime that no upstream will patch is the opposite of that posture.

The one thing to do before the date

Not "upgrade everything." Find out what you are actually running, everywhere, and write it down. One command on each host (php -v) gives you the runtime version. Your composer.json or lock file gives you the constraint. Put the two side by side for every service you own and you have a map. The map tells you which systems are a five-minute bump and which are a fortnight of regression testing. Without the map, every estimate is fiction and every deadline is a surprise.

Once you have the map, the upgrade itself is ordinary engineering. Move to 8.3 at least — and 8.4, supported into 2028, buys you the most runway for the same testing effort. Run the framework’s upgrade tooling, clear the deprecation warnings, put it through CI, ship it behind your normal release process. The work is not hard. It is just work, and work needs to be scheduled before the month it is due. If the map comes back ugly — a legacy application nobody owns, a runtime pinned by a dependency that itself went unsupported years ago — that is the conversation worth having now, not in a change freeze in December.

Mapping an estate and running the upgrades is exactly the kind of work my services exist to absorb.

Advisory engagements are priced as fixed-scope reviews or a monthly fractional retainer; delivery is quoted per programme once the estate is mapped.

If you know the upgrade needs doing but do not have the hands to do it before the freeze, that is where my sister-brand build and ops capacity comes in — we can take the runtime and framework upgrades across your estate as a scoped piece of delivery. Either way, get the map done first. The date is 31 December 2026.

Build and rescue work

Hands-on delivery of this kind is handled by Sixteen Pillars Studio.

Free interactive tool

Website compliance checklist

What your site has to do, based on what it actually does

Answer as much or as little as you like — the list builds as you go. Nothing is stored against your name and no email is required.

Can you trust the architecture you have?

Architecture diagrams rarely show the reality of how systems actually operate. An independent review establishes what is really there.