Security support for PHP 8.2 ends on 31 December 2026. If your website or internal system runs on it, here is what changes, why it matters, and the options for moving forward.
PHP powers a large share of the web, from small business websites to bespoke internal systems. Every PHP release branch has a fixed lifespan, and on 31 December 2026 security support for PHP 8.2 comes to an end.
How PHP support works
According to the official PHP project, each release branch is fully supported for two years from its first stable release, then receives critical security fixes only for two further years. After those four years, the branch reaches end of life and receives no updates at all.
PHP 8.2 was first released on 8 December 2022. Its active support ended on 31 December 2024, and its security support ends on 31 December 2026. PHP 8.1 and every earlier version have already reached end of life.
Why end of life matters
Once a version is no longer supported, newly discovered vulnerabilities in it will not be fixed. The PHP project itself warns that users of end-of-life releases "may be exposed to unpatched security vulnerabilities". For a business, that can mean:
- Security risk: attackers actively scan the internet for servers running outdated software.
- Compliance pressure: customers, insurers and auditors increasingly ask whether your systems run supported software.
- Hosting changes: hosting providers often retire old PHP versions, sometimes at short notice.
- Growing technical debt: the further behind a codebase falls, the harder and more expensive it becomes to upgrade.
Check which version you're running
Your hosting control panel usually shows the PHP version for each site. Developers can run php -v on the server. If you're not sure, ask your developer or hosting provider, or get in touch with us and we'll help you find out.
Your options
1. Upgrade to a supported PHP version
At the time of writing, PHP 8.3, 8.4 and 8.5 are all supported, with PHP 8.5 receiving security fixes until the end of 2029. For well-maintained code, an upgrade can be straightforward; for older code, it may surface deprecated features that need rewriting.
2. Migrate incrementally
If downtime isn't an option, systems can be modernised component by component, with the existing application staying live until each part is safely replaced.
3. Rewrite on a modern stack
For ageing applications that are hard to maintain, a structured rewrite in a modern language can remove years of accumulated risk at once.
How diam can help
Our PHP and legacy migration service covers security audits, upgrades, incremental migrations and full rewrites. Every engagement begins with a free consultation.
Source: PHP supported versions, php.net. Dates correct at the time of publication.