PHP 8.2 end of life
PHP 8.2 end of life is 31 December 2026. Since 31 December 2024 it has received critical security fixes only, and after 31 December 2026 the PHP project will ship no more 8.2 releases. The latest is 8.2.35, released on 22 October 2026. You can upgrade to PHP 8.3, 8.4 or 8.5, or keep 8.2 patched with third-party security support.
What now
Which vendors provide PHP 8.2 security patches after 31 December 2026?
PHP Extended Support: Security Patches for 7.4 to 8.3- End of life
- 31 December 2026
- Released
- Dec 2022
- Final release
- 8.2.35 (latest)
- 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 17 November 2026.
Last reviewed
PHP versions: release and end-of-life dates
| Version | Released | End of life | Status |
|---|---|---|---|
| PHP 8.2 (this page) | 8 Dec 2022 | 31 December 2026 | Approaching |
End-of-life dates are published by each project and checked against endoflife.date.
What actually stops on 31 December 2026
- Security releases on the 8.2 line. php.net lists security support for PHP 8.2 until 31 December 2026, and 8.2.35 (22 October 2026) is the latest release today.
- Fixes for vulnerabilities reported after that date. A flaw found in 8.2 later is fixed in the supported branches only.
- Triage of new reports against 8.2 by the PHP security team.
- Nothing stops earlier: active support (bug fixes) for 8.2 already ended on 31 December 2024.
What actually breaks in the upgrade
Which PHP line to move to
php.net lists PHP 8.3 with security support until 31 December 2027, PHP 8.4 until 31 December 2028 and PHP 8.5 until 31 December 2029. 8.3 is the smallest step from 8.2 but leaves about a year of support; 8.4 or 8.5 give a longer runway.
Read the project's migration guide first
php.net publishes a migration guide for each step, including PHP 8.2 to 8.3 and onward. Run your test suite with deprecation notices visible on the target version before you switch production, and check that your framework and extensions support it. php.net supported versions.
PHP 8.4 active support ends the same day
php.net lists 31 December 2026 as the end of active support for PHP 8.4, the same day security support for 8.2 ends. 8.4 then gets security fixes only until 31 December 2028.
Upgrade to PHP 8.3 or 8.4, or stay on 8.2?
Upgrade to 8.4 or 8.5 if the application allows it, and stay on 8.2 only with patches if something holds it back. The table compares the lines using the dates on php.net, checked 17 November 2026.
| Line | Active support ends | Security support ends |
|---|---|---|
| PHP 8.2 | 31 Dec 2024 (ended) | 31 Dec 2026 |
| PHP 8.3 | 31 Dec 2025 (ended) | 31 Dec 2027 |
| PHP 8.4 | 31 Dec 2026 | 31 Dec 2028 |
| PHP 8.5 | 31 Dec 2027 | 31 Dec 2029 |
CVEs in PHP 8.2 fixed in 2026
Seven CVEs fixed in 8.2.32 to 8.2.34 show the pace of PHP security releases in 2026. Each record below was checked on the CVE API on 17 November 2026 and lists PHP 8.2 as affected. This is a sample of the 2026 fixes, not a complete list.
| CVE | What it is | Severity (CVSS) | Fixed in 8.2 |
|---|---|---|---|
| CVE-2026-17543 | SQL injection in ext-pgsql via an E'...' backslash breakout | High (8.1, CVSS 4.0) | 8.2.33 |
| CVE-2026-91765 | SOAP: unbounded recursion in server-side cleanup_xml_node | High (7.5, CVSS 3.1) | 8.2.34 |
| CVE-2026-91768 | IPv6 ACL bypass in FastCGI listen.allowed_clients | Medium (6.5) | 8.2.34 |
| CVE-2026-91767 | Heap buffer overflow in php_openssl_matches_wildcard_name on a crafted wildcard CN | Medium (6.5) | 8.2.34 |
| CVE-2026-14355 | Memory corruption in openssl_encrypt with AES-WRAP-PAD | Medium (5.6) | 8.2.32 |
| CVE-2026-7260 | Stack overflow in phar with circular symlinks | Medium (5.4, CVSS 4.0) | 8.2.33 |
| CVE-2026-6103 | Phar TAR phar_tar_number() integer overflow, archive entry injection | Medium (4.3) | 8.2.34 |
Source: cveawg.mitre.org CVE records and php.net/ChangeLog-8.php, checked 17 November 2026. After 31 December 2026 fixes like these will no longer ship for 8.2.
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 years of security support left, after testing framework and extension compatibility. | Scales with framework version, extensions and test coverage | Engineering time | The default destination. 8.4 is supported to 31 Dec 2028 and 8.5 to 31 Dec 2029. |
| Upgrade to PHP 8.3 | The smallest step from 8.2. | Scales with extensions and test coverage | Engineering time | An interim step. Security support ends 31 Dec 2027. |
| Extended security support | Backported fixes for PHP 8.2 after 31 December 2026: 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 newly found vulnerabilities after 31 December 2026. | None | Zero now | PHP applications are usually internet-facing. A poor place to carry risk. |
What OSSeva does for PHP 8.2
OSSeva patches this line
OSSeva backports security fixes to PHP 8.2 once the PHP project stops on 31 December 2026, and already patches PHP 7.4 and 8.1. Other PHP versions are assessed case by case.
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.
When is PHP 8.2 end of life?
31 December 2026, per php.net. PHP 8.2 has been in security-fixes-only support since 31 December 2024.
What happens to PHP 8.2 on 31 December 2026?
The PHP project stops releasing security fixes for the 8.2 line. 8.2.35 (22 October 2026) is the latest release today, and vulnerabilities found later are fixed only in the branches that are still supported.
Should I upgrade PHP 8.2 to 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.3 is the smallest step, but its security support ends on 31 December 2027.
Is PHP 8.2 still safe to use?
Until 31 December 2026 it still gets critical security fixes. Afterwards it does not, so a site that stays on 8.2 needs third-party security patches or an upgrade.
Can I get security patches for PHP 8.2 after it ends?
Not from the PHP project. Third-party extended support, including OSSeva's, backports fixes to 8.2 after 31 December 2026.
Get a quote
Still running PHP 8.2?
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?