PHP 8.1 end of life
PHP 8.1 reached end of life on 31 December 2025, and 8.1.34, released on 18 December 2025, was its last release. The PHP project has shipped no security fix for 8.1 since. You can upgrade to PHP 8.4, 8.5 or 8.6, or keep 8.1 patched: OSSeva patches PHP 8.1 after end of life.
What now
Which vendors provide PHP 8.1 security patches now that support has ended?
PHP Extended Support: Security Patches for 7.4 to 8.3- End of life
- 31 December 2025
- Released
- Nov 2021
- Final release
- 8.1.34
- Successor
- PHP 8.4 or 8.5
Date published by php.net supported versions. We do not publish a lifecycle date we cannot source. Dates checked on php.net and endoflife.date on 19 November 2026.
Last reviewed
PHP versions: release and end-of-life dates
| Version | Released | End of life | Status |
|---|---|---|---|
| PHP 8.2 | 8 Dec 2022 | 31 December 2026 | Approaching |
| PHP 8.1 (this page) | 25 Nov 2021 | 31 December 2025 | End of life |
End-of-life dates are published by each project and checked against endoflife.date.
What actually stops on 31 December 2025
- Security releases on the 8.1 line. php.net lists 31 December 2025 as the end date and 8.1.34 as the last release.
- Fixes for vulnerabilities reported after that date. Flaws found in PHP since are fixed in the supported branches only.
- Nothing stops earlier: active support (bug fixes) for 8.1 ended on 25 November 2023 per endoflife.date.
What actually breaks in the upgrade
Which PHP line to move to
php.net lists PHP 8.2 with security support until 31 December 2026, 8.3 until 31 December 2027, 8.4 until 31 December 2028, 8.5 until 31 December 2029 and 8.6, released on 19 November 2026, until 31 December 2030. 8.5 or 8.6 gives the longest runway; 8.4 is a common step if a framework does not yet support the newer lines. php.net supported versions.
Dynamic properties are deprecated from 8.2
The PHP 8.2 migration guide deprecates creating dynamic properties unless the class has #[\AllowDynamicProperties], and deprecates utf8_encode and utf8_decode and "${var}" string interpolation. Older frameworks and plugins trigger these in volume, which is the first thing to see on the way off 8.1. PHP 8.2 deprecated features.
Test on 8.4 with deprecation notices visible
Run the suite with E_DEPRECATED on in the target version and check that your framework and extensions support it. Fixing deprecations on 8.2 first makes the later steps smaller.
PHP 8.1 and the lines above it
Dates are from php.net, with active-support dates for 8.1 from endoflife.date, read on 19 November 2026.
| Line | Released | Active support ends | Security support ends |
|---|---|---|---|
| PHP 8.1 | 25 Nov 2021 | 25 Nov 2023 | 31 Dec 2025 (ended, last release 8.1.34) |
| PHP 8.2 | 8 Dec 2022 | 31 Dec 2024 | 31 Dec 2026 |
| PHP 8.3 | 23 Nov 2023 | 31 Dec 2025 | 31 Dec 2027 |
| PHP 8.4 | 21 Nov 2024 | 31 Dec 2026 | 31 Dec 2028 |
| PHP 8.5 | 20 Nov 2025 | 31 Dec 2027 | 31 Dec 2029 |
| PHP 8.6 | 19 Nov 2026 | 31 Dec 2028 | 31 Dec 2030 |
What is specific to PHP 8.1
PHP 8.1 introduced enumerations, readonly properties, first-class callable syntax, fibers, pure intersection types, the never return type and objects as default parameter values (new in initializers), per its release page on php.net. Applications written for 8.1 often lean on enums and readonly properties, and PHP 8.2 added readonly classes on top.
The first things to break on the way up are deprecations, not removals. The PHP 8.2 migration guide deprecates creating dynamic properties unless the class opts in with #[\AllowDynamicProperties], deprecates utf8_encode and utf8_decode, and deprecates the "${var}" and "${expr}" forms of string interpolation. The 8.3 guide adds the deprecation of assert_options() and the MT_RAND_PHP variant. None stops the code, but each writes a notice, and the notices arrive in bulk on an older codebase.
Ubuntu 22.04 ships PHP 8.1: packages.ubuntu.com lists php8.1 at 8.1.2-1ubuntu2.28 for jammy, read on 19 November 2026. That version string is far behind the upstream 8.1.34, which does not mean the Ubuntu build lacks fixes, because Ubuntu backports into its own package. It does mean a scanner reading the version string and a scanner reading Ubuntu's security data can reach different conclusions about the same host.
Scanners can also be silent for the wrong reason. The CVE record for CVE-2026-17543, an SQL injection in ext-pgsql fixed in 8.2.33, lists PHP 8.2.* to 8.5.* and says nothing about 8.1 (record at cveawg.mitre.org; advisory GHSA-7qpv-r5mr-78m4 on php/php-src). A scan that matches against that record will not flag 8.1, and its silence is not evidence that 8.1 is unaffected. We do not list CVEs for 8.1 because neither source names the line.
Sources: php.net/releases/8.1, php.net/manual/en/migration82.deprecated and migration83.deprecated, php.net/ChangeLog-8.php, packages.ubuntu.com, cveawg.mitre.org. All read on 19 November 2026.
Your options, costed honestly
Including the ones that do not involve buying anything from us.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Upgrade to PHP 8.4 or 8.5 | Move to a line with security support until 31 December 2028 (8.4) or 2029 (8.5). | Scales with framework version, extensions and test coverage | Engineering time | The default destination. |
| Upgrade to PHP 8.2 or 8.3 | The smaller steps from 8.1. | Scales with extensions and test coverage | Engineering time | Interim only. 8.2 ends 31 December 2026 and 8.3 on 31 December 2027. |
| Extended security support | Backported fixes for PHP 8.1: Critical CVEs within 48 hours, High within 7 days. | Starts from your current version | Subscription, priced per application runtime | For applications held by a framework release, vendor certification or a release freeze. |
| Stay unpatched | No fixes for vulnerabilities found since 31 December 2025. | None | Zero now | PHP applications are usually internet-facing. A poor place to carry risk. |
What OSSeva does for PHP 8.1
OSSeva patches this line
OSSeva patches PHP 8.1 after end of life, and also PHP 7.4, with 8.2 and 8.3 covered once the PHP project stops. Other PHP versions are assessed case by case through a version coverage check.
PHP extended supportWhat your auditor will say
Requirement 6.3.3. Payment pages and APIs on an unsupported runtime need patched components or a documented compensating control.
CC7.1. Auditors look for evidence that production runtimes receive security fixes.
Is PHP 8.1 end of life?
Yes. PHP 8.1 reached end of life on 31 December 2025 per php.net, and its last release was 8.1.34 on 18 December 2025.
What was the last PHP 8.1 release?
8.1.34, released on 18 December 2025 according to the php.net changelog.
Is PHP 8.1 still safe to use?
It runs, but the PHP project has issued no security fix for it since 31 December 2025, so new vulnerabilities stay open unless a third party patches them.
Should I upgrade PHP 8.1 to 8.2, 8.3 or 8.4?
8.4 or 8.5 if you can: 8.4 has security support until 31 December 2028 and 8.5 until 31 December 2029. 8.2 ends on 31 December 2026, so it is a short stop.
Can I get security patches for PHP 8.1 after end of life?
Not from the PHP project. OSSeva patches PHP 8.1 after end of life, priced per application runtime. Other PHP versions are assessed through a version coverage check.
Does Ubuntu 22.04 still get PHP 8.1 fixes?
The php8.1 package on Ubuntu 22.04 is built and updated by Ubuntu and shows version 8.1.2-1ubuntu2.28 on packages.ubuntu.com. Its patching follows Ubuntu's own security notices, not the PHP project's.
Get a quote
Still running PHP 8.1?
Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.
Prefer to talk or read more first?